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.

Sign up for GitHub

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

Jump to bottom

Status page returns 503 when alerting cannot find its health task in Task Manager #98796

Closed
mikecote opened this issue Apr 29, 2021 · 1 comment · Fixed by #99564
Closed

Status page returns 503 when alerting cannot find its health task in Task Manager #98796

mikecote opened this issue Apr 29, 2021 · 1 comment · Fixed by #99564
Assignees
@YulNaumenko
Labels
bug Fixes for quality problems that affect the customer experience Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

See comment #94968 (comment).

It seems whenever the health status of the alerting plugin refreshes and the alerting health task doesn't exist, we cause the status page to return a 503 error. This edge case seems to only happen in tests when using esArchiver, which deletes all existing tasks, but the framework should still report its health accordingly.
@mikecote mikecote added bug Fixes for quality problems that affect the customer experience Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Apr 29, 2021
@elasticmachine
Copy link
Contributor

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

@mikecote mikecote mentioned this issue Apr 29, 2021
Merged
@YulNaumenko YulNaumenko self-assigned this May 5, 2021
@YulNaumenko YulNaumenko mentioned this issue May 7, 2021
Merged
@gmmorris gmmorris mentioned this issue Jun 15, 2021
Closed
@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
Assignees

@YulNaumenko YulNaumenko

Labels
bug Fixes for quality problems that affect the customer experience Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
4 participants
@kobelb @mikecote @elasticmachine @YulNaumenko