-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SIEM] [Detections] Renames Signals to Alerts #67731
Conversation
Pinging @elastic/siem (Team:SIEM) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment about some potentially missed translations, but: LGTM! Very minimal logical changes so review was a breeze.
Checked it out locally and verified:
- creating rules and generating
signalsalerts - creating/saving timelines
- route redirects
- general clicking around and trying to break things
} | ||
); | ||
|
||
export const SIGNAL_GET_NAME_FAILURE = i18n.translate( | ||
'xpack.siem.containers.detectionEngine.signals.errorGetSignalDescription', | ||
'xpack.siem.containers.detectionEngine.alerts.errorGetAlertDescription', | ||
{ | ||
defaultMessage: 'Failed to get signal index name', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this (and the one below it) be changed? I saw your note about not touching signalsIndex
but I see other similar strings being changed so 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah it was tough to draw the line with some of these, but I left this and the one below as is since it was referencing the signals index and we're not quite sure what that's going to be named yet.
{ | ||
defaultMessage: 'Failed to get signal index name', | ||
} | ||
); | ||
|
||
export const SIGNAL_POST_FAILURE = i18n.translate( | ||
'xpack.siem.containers.detectionEngine.signals.errorPostSignalDescription', | ||
'xpack.siem.containers.detectionEngine.alerts.errorPostAlertDescription', | ||
{ | ||
defaultMessage: 'Failed to create signal index', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto ^^
@@ -7,17 +7,17 @@ | |||
export interface BasicSignals { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this one should technically be BasicAlerts
. Buttt we could also replace it with an inline { signal: AbortSignal }
in the few places it's used, too. 🤷♂️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I was 🤷♂️ on that as well as I couldn't tell if BasicSignal
was meant to refer to the AbortSignal
or SignalSignal. I agree going inline might just be for the best here.
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
## Summary Resolves elastic#65944 Renames `Signals` -> `Alerts` on the main Detection Engine page. Including: * Timeline Event Selector * Alerts Histogram * Alerts Table Does not include: * `Detections` -> `Alerts` navigation rename * `SignalsByCategory` rename as there already exists an `AlertsByCategory`, verify changing to `ExternalAlertsByCategory` * Anything server-side or related to `siemSignalsIndex` ### Checklist - [X] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/master/packages/kbn-i18n/README.md) - [X] [Unit or functional tests](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#cross-browser-compatibility) were updated or added to match the most common scenarios
## Summary Resolves #65944 Renames `Signals` -> `Alerts` on the main Detection Engine page. Including: * Timeline Event Selector * Alerts Histogram * Alerts Table Does not include: * `Detections` -> `Alerts` navigation rename * `SignalsByCategory` rename as there already exists an `AlertsByCategory`, verify changing to `ExternalAlertsByCategory` * Anything server-side or related to `siemSignalsIndex` ### Checklist - [X] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/master/packages/kbn-i18n/README.md) - [X] [Unit or functional tests](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md#cross-browser-compatibility) were updated or added to match the most common scenarios
Pinging @elastic/security-solution (Team: SecuritySolution) |
Summary
Resolves #65944
Renames
Signals
->Alerts
on the main Detection Engine page. Including:Does not include:
Detections
->Alerts
navigation renameSignalsByCategory
rename as there already exists anAlertsByCategory
, verify changing toExternalAlertsByCategory
siemSignalsIndex
Checklist