-
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
[Alerting] Surface rule execution durations in rule details #114616
Comments
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
@mdefazio I have split out the Rule Details view into its own issue. When you are ready with the mockup, can you post to this issue? Thanks! |
Here are some initial thoughts on how to show these values in the detail page. I've taken some cues from Security's Host page and how they show metrics there (with some obvious slight differences since we want to show 3 values in relation to a single chart, compared to 1 value per chart on the Hosts page). I'm including a dropdown to provide the user the ability to show last 60, last 120, etc (or whatever count we determine is best here). This may be out of scope, so i'm fine omitting it for now. We may want some indication that we are only showing the last 60 executions (assuming this is also the case for the alerts table on this page)? I've grayed out the alert table as these mockups are only meant to focus on the addition of the metrics above the table. Video walkthrough: Screenshots:Only a few executions Warning message within values |
POC here
As part of the effort to address long-running rules, we would like to surface rule execution duration information (currently stored in the event log) in the UI.
With this PR, we are surfacing it in the Rule Management View. This issue covers surfacing it in the Rule Details view.
In the rule details view. We can calculate statistics for avg/min/max duration for all the retrieved event log entries in the
getAlertInstanceSummary
function and show them in the UI. We could also show a warning if the average execution duration for the rule greatly exceeds the configured schedule (for example, if the rule is scheduled to run every minute and the average duration is 25 minutes, we should tell the user!)Example:
The text was updated successfully, but these errors were encountered: