-
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
Alerts are not recovered correctly in ICMP monitoring due to 'ping timeout' #187592
Comments
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
Add error terminal.
|
NOTE: Seems like there is a lot of additional detail in the linked discuss thread, it might be a good idea to try to capture more of that here in this issue. We'll try to recreate this and see what we can discover. |
Kibana version: 8.13.2
Elasticsearch version: 8.13.2
Describe the bug:
Alerts configured in the observability rule do not recover correctly when the condition that triggered them is no longer true. This appears to be bug-like behavior.
Steps to reproduce:
Configure a rule in Kibana to monitor ICMP status with condition
MATCHING MONITORS ARE DOWN >= 3 times WITHIN last 10 minutes.
Shut down one of the monitored hosts to generate a
"ping timeout".
Note that the alert fires correctly but does not recover when the host comes back online.
Expected behavior:
Alerts should automatically recover when the original condition that triggered them is no longer met.
Additional attachment discuss created for the current case that contains more details, screenshots, logs, etc.
https://discuss.elastic.co/t/problem-with-alerts-recovered/362036
The text was updated successfully, but these errors were encountered: