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

Document Kibana Alert Statuses #101521

Closed
stefnestor opened this issue Jun 7, 2021 · 3 comments · Fixed by #103725
Closed

Document Kibana Alert Statuses #101521

stefnestor opened this issue Jun 7, 2021 · 3 comments · Fixed by #103725
Assignees
Labels
docs Feature:Alerting needs_docs Project:ImproveAlertingGettingStartedUX Alerting team project for making the experience of getting started with alerting easier. Team:Docs Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@stefnestor
Copy link
Contributor

Kibana version: 7.12-7.13

Howdy! It appears there is a defined categorization of Kibana Alert statuses from #51099 by @pmuellr on #75553 : [active, error, ok, pending, unknown]

However I'm unable to find their definitions in the documentation (expected somewhere around here or here). I may just be blind (if so, sorry in advance).

image

I'm particularly interested in the difference between active & ok, error & unknown, and what pending means in general.

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-docs (Team:Docs)

@mikecote mikecote added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Jun 16, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@pmuellr
Copy link
Member

pmuellr commented Jun 18, 2021

Ya, we need to doc this. I'm going to start pointing folks asking to this issue, and here's a quick summary:

  • active - the conditions for the rule have been met, and the associated actions should be invoked
  • ok - the conditions for the rule had previously been met, but no longer are being met. This will change to recovered in a future release (see PR referenced below).
  • error - an error was encountered when the rule was executed
  • pending - the rule has not yet executed; it was either just created, or just enabled after being disabled
  • unknown - fallback internally when calculating the status; if this is observed, there is likely some kind of problem with the alerting code

Some improvements currently merged to 7.x, so hopefully available in 7.14: #98135

@YulNaumenko YulNaumenko self-assigned this Jun 29, 2021
@gmmorris gmmorris added the Project:ImproveAlertingGettingStartedUX Alerting team project for making the experience of getting started with alerting easier. label Jun 30, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Feature:Alerting needs_docs Project:ImproveAlertingGettingStartedUX Alerting team project for making the experience of getting started with alerting easier. Team:Docs Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
8 participants