Skip to content
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

Open
alytkowski opened this issue Dec 2, 2022 · 8 comments
Open

Add alert status for WARNING/CRITICAL #146893

alytkowski opened this issue Dec 2, 2022 · 8 comments
Labels
Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@alytkowski
Copy link

In the current Kibana rules configuration, it's possible to configure different thresholds for Metric rules for "Warning" and "Alert".
obraz

However, when the metric is above the Warning/Alert threshold, it is seen as the same in the Alerts section (the Alert Status - Active).
obraz

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.

@botelastic botelastic bot added the needs-team Issues missing a team label label Dec 2, 2022
@dmlemeshko dmlemeshko added the Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" label Dec 2, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/actionable-observability (Team: Actionable Observability)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 2, 2022
@kdelemme kdelemme added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Dec 7, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@kdelemme kdelemme removed the Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" label Dec 7, 2022
@XavierM
Copy link
Contributor

XavierM commented Dec 8, 2022

@vinaychandrasekhar and @shanisagiv1, this issue sound to be more a product question than a fix that the engineer can provide.

@XavierM
Copy link
Contributor

XavierM commented Dec 8, 2022

@alytkowski, I think the reason should give you the why of the existence of this alert.

@alytkowski
Copy link
Author

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.

@alytkowski
Copy link
Author

@alytkowski, I think the reason should give you the why of the existence of this alert.

About the reason - It would be nice if users had the possibility to set a custom reason for every rule.

@XavierM
Copy link
Contributor

XavierM commented Jan 5, 2023

@grabowskit What do you think?

@shanisagiv1
Copy link

shanisagiv1 commented Jan 10, 2023

@XavierM
I guess the "why" (e.g threshold violation) is diff than the severity (warning/critical) or the status (active/recovered). how is the warning/critical status saved today? Is it a separate field? Can we present it as a new column? Can we unify these fields so we'll have a single Status column : [Active, Active - Warning , Active - Critical, Recovered]. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

6 participants