-
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
[RAC] [Observability] Use simpler alert severity level mapping #109068
Conversation
0700540
to
1743e6e
Compare
1743e6e
to
a64b656
Compare
…and shown in the Observability alerts table
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
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.
Uptime changes LGTM
Pinging @elastic/apm-ui (Team:apm) |
Pinging @elastic/uptime (Team:uptime) |
@elasticmachine merge upstream |
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.
Looks good, there's a commented line we should remove.
x-pack/plugins/uptime/server/lib/alerts/duration_anomaly.test.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/server/lib/alerts/register_transaction_duration_anomaly_alert_type.ts
Outdated
Show resolved
Hide resolved
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.
APM changes look good.
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.
LGTM
💚 Build SucceededMetrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: cc @mgiota |
…ic#109068) * [RAC][Observability] remove severity fields from mapping keep only ALERT_SEVERITY * temporarily remove severity value occurences * remove ALERT_SEVERITY_VALUE occurences, this value is not being read and shown in the Observability alerts table * remove duplicate ALERT_SEVERITY identifier Co-authored-by: Kibana Machine <[email protected]>
…ic#109068) * [RAC][Observability] remove severity fields from mapping keep only ALERT_SEVERITY * temporarily remove severity value occurences * remove ALERT_SEVERITY_VALUE occurences, this value is not being read and shown in the Observability alerts table * remove duplicate ALERT_SEVERITY identifier Co-authored-by: Kibana Machine <[email protected]>
…) (#109172) * [RAC][Observability] remove severity fields from mapping keep only ALERT_SEVERITY * temporarily remove severity value occurences * remove ALERT_SEVERITY_VALUE occurences, this value is not being read and shown in the Observability alerts table * remove duplicate ALERT_SEVERITY identifier Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: mgiota <[email protected]>
…) (#109171) * [RAC][Observability] remove severity fields from mapping keep only ALERT_SEVERITY * temporarily remove severity value occurences * remove ALERT_SEVERITY_VALUE occurences, this value is not being read and shown in the Observability alerts table * remove duplicate ALERT_SEVERITY identifier Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: mgiota <[email protected]>
📝 Summary
Fixes #109075
In order to comply with the Alerts-as-Data-Schema-Fields, we are removing
kibana.alert.severity.level
andkibana.alert.severity.value
and keep onlykibana.alert.severity
.Acceptance criteria
ALERT_SEVERITY_VALUE
and all usages are removed for nowALERT_SEVERITY_LEVEL
is renamed toALERT_SEVERITY
and it will be a keyword field calledkibana.alert.severity
Notes
signal.rule.severity
and they would like to alias that field askibana.alert.severity
(as opposed to aliasing it as kibana.alert.severity.level).