-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 Simple (200 OK) Health Check Endpoint #2034
Comments
What do you mean by "hack around"? The status page would work for a simple health check. |
The |
Ah! I remembered adding those, but didn't see them when looking through the api v1 impl. My bad :) |
In version 0.19.0 / 2019-09-03, those paths return 404 page not found. |
Not for me. |
So why don't you document this fundamental feature on your GitHub page so other people can run into the same problem I'm having? |
@kaizen1 do you want to prepare a pull reuqest to add documentation to prometheus.io/docs. prometheus/prometheus#5737 should be a good sample, but I guess this pull request would need to point at https://github.com/prometheus/docs/tree/master/content/docs/alerting directly. |
I couldn't get the suggested URLs to return 200 OK, so I can't document an unverifiable solution. That was why I asked the maintainer to document it. |
@kaizen1 can you follow up on the user mailing list with the details of your setup (configuration, logs, version, ...) and the exact response from AlertManager? |
I've attached the requested information. Note: Alertmanager is working fine. It's sending alerts via PagerDuty. I can get to the Alertmanager web ui thru my reverse proxy. I can curl from inside my network. but the /ready endpoint returns 404 page not found. See attached for other curl results. Thanks. |
It's |
I had already tried /-/ready same error as previously reported. |
The mailing list is the appropriate venue for usage questions. |
Feature Request:
Add an http endpoint where we can do a simple 200 OK health check.
Many of us run behind a reverse proxy. We're forced to hack around with regex now for health checking. It's not working that well behind HAProxy.
For example, 10.128.0.4:9093/
Should return 200 OK to denote the server is up.
The text was updated successfully, but these errors were encountered: