[Logs UI] Support runtime fields in the log threshold alert#97603
Conversation
|
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
Kerry350
left a comment
There was a problem hiding this comment.
The changes here work great 🎉
I've requested changes as the updates to the chart previews are missing, and shipping one without the other looks broken with 0s:
It should just be a case of updating the calls here: https://github.com/elastic/kibana/blob/master/x-pack/plugins/infra/server/lib/alerting/log_threshold/log_threshold_chart_preview.ts#L54, it shares the same functions from the executor.
| }; | ||
|
|
||
| const body = { | ||
| const body: estypes.SearchRequest['body'] = { |
Oh, good catch. That's the cost of allowing |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @weltenwort |
…97603) This enhances the log threshold alert executor to include the corresponding runtime mappings in the queries if the source is configured to use a KIP.
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
…97693) This enhances the log threshold alert executor to include the corresponding runtime mappings in the queries if the source is configured to use a KIP. Co-authored-by: Felix Stürmer <weltenwort@users.noreply.github.com>



📝 Summary
This enhances the log threshold alert executor to include the corresponding runtime mappings in the queries if the source is configured to use a KIP.
relates to #92881
🎨 Previews
runtime field in a condition

runtime field in a group

alerts with condition and group runtime fields fire
