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
Postgres floating-point exception but health check was ok #2958
Comments
Thanks for reporting here. I do not think you should rely on the /_health/ endpoint in Sentry as a source of truth, I just took a look and it seems to be pretty out of date. I'll backlog this item to improve the endpoint to cover more of the main components of self-hosted. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Self-Hosted Version
24.3.0
CPU Architecture
x86_64
Docker Version
25.0.3
Docker Compose Version
2.25.0
Steps to Reproduce
You try to load any admin page like
https://sentry.domain.com/organizations/[ORGA]/projects/
And receive a HTTP Code 500
But when you call
https://sentry.domain.com/_health/
You still get an HTTP Code 200 and the message: ok
Expected Result
When there is an error which causes all http request to fail with a HTTP Code 500, the health endpoint should also reflect this.
Actual Result
We experienced a strange error with Sentry.
The PostgreSQL Database started to respond with an error to all SELECT set_config queries.
Web, Cron, Worker all show the same errors caused by postgres.
All API endpoints, Admin interface etc have thrown server errors and a HTTP Code 500 but /_health/ was returning HTTP 200 and a OK.
The problem lastet for 5 hours because monitoring thought the service is still alive.
All services were running.
Restart the instance and all Sentry services fixed the problem.
docker compose logs postgres:
docker compose logs web:
Event ID
No response
The text was updated successfully, but these errors were encountered: