-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Doc bug as to how to edit Monitoring alerts #101346
Comments
Related to #91145 |
Pinging @elastic/stack-monitoring (Team:Monitoring) |
@msimos Thank you for filling this issue! Yes, currently Stack Monitoring alerts can only be edited through the SM ui via "Enter setup mode" button: We do however have plans to also enable managing/creating/deleting/editing in I think this PR should also change/rebrand the "alert" terminology to rules/alerting, so it can be consistent with other apps eg: #100918 cc: @lcawl |
Kibana version:
7.13
Describe the bug:
This URL:
https://www.elastic.co/guide/en/kibana/current/kibana-alerts.html#kibana-alerts
States:
When you open Stack Monitoring, the preconfigured Kibana alerts are created automatically. If you collect monitoring data from multiple clusters, these alerts can search, detect, and notify on various conditions across the clusters. The alerts are visible alongside your existing Watcher cluster alerts. You can view details about the alerts that are active and view health and performance data for Elasticsearch, Logstash, and Beats in real time, as well as analyze past performance. You can also modify active alerts.
Then it states:
To review and modify all the available alerts, use Alerts and Actions in Stack Management.
The alert can be modified but only the actions can be changed & interval. And you cannot edit the built in alerts from Alerts and Actions in Stack Management. It must be done at the Stack Monitoring page. So I think there needs to be clarification about both of these.
Screenshots (if relevant):
From Alerts and Actions in Stack Management there is no edit button for any of the built in provided alerts as an example:
However you can modify the alert from Stack Monitoring Cluster Overview:
The text was updated successfully, but these errors were encountered: