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

Have the status_page route return a 503 when the kibana status is red #72831

Closed
pgayvallet opened this issue Jul 22, 2020 · 2 comments
Closed

Have the status_page route return a 503 when the kibana status is red #72831

pgayvallet opened this issue Jul 22, 2020 · 2 comments
Labels
enhancement New value added to drive a business result Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@pgayvallet
Copy link
Contributor

Original discussion: #72017 (comment)

In #72017 we migrated the status page to core. However the legacy status page was responding with an http code of 503 when the kibana status is red.

This is something that could not be done directly in #72017 as the server-side API was not yet migrated to core.

When this is done, we should adapt the status_page server-side route to correctly return 503 until kibana is green.
@pgayvallet pgayvallet added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform enhancement New value added to drive a business result labels Jul 22, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

@pgayvallet pgayvallet mentioned this issue Jul 22, 2020
Merged
2 tasks
@joshdover joshdover mentioned this issue Jul 22, 2020
Closed
15 tasks
@joshdover joshdover self-assigned this Sep 22, 2020
@joshdover joshdover removed their assignment Dec 2, 2020
@pgayvallet
Copy link
Contributor Author

This is not necessary anymore. any health check should be performed against the status API directly, not the status page.

@pgayvallet pgayvallet closed this as not planned Won't fix, can't repro, duplicate, stale Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New value added to drive a business result Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pgayvallet @joshdover @elasticmachine