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
Add alert status for WARNING/CRITICAL #146893
Comments
Pinging @elastic/actionable-observability (Team: Actionable Observability) |
Pinging @elastic/response-ops (Team:ResponseOps) |
@vinaychandrasekhar and @shanisagiv1, this issue sound to be more a product question than a fix that the engineer can provide. |
@alytkowski, I think the reason should give you the why of the existence of this alert. |
Yes, that's right, but what is the point of the Warning threshold if Kibana doesn't show Warning and the alert is exactly the same for Warning/Alert. |
About the reason - It would be nice if users had the possibility to set a custom reason for every rule. |
@grabowskit What do you think? |
@XavierM |
In the current Kibana rules configuration, it's possible to configure different thresholds for Metric rules for "Warning" and "Alert".
However, when the metric is above the Warning/Alert threshold, it is seen as the same in the Alerts section (the Alert Status - Active).
What I would suggest is to have different Alert status (Warning and Critical instead of "Active", which doesn't say much).
Also, the statuses should be coloured accordingly yellow/red for warning and critical.
The text was updated successfully, but these errors were encountered: