-
Notifications
You must be signed in to change notification settings - Fork 887
Expose healthcheck data in Prometheus metrics #10678
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
Comments
Okay so I've taken a look at this and found a few interesting points:
Given the refactor + API key issue, I want to ask if this still seems like a positive ROI on this work. I see the value in the metrics but given this was suppose to be a "quick and easy" one I want to make sure we want to do these changes required for this data. |
Work in progress PR here: #10921 |
So @sreya and I synced on this - given the complexity it adds to the codebase vs the value returned we don't think it's a good idea to do this right now. The background job work just changes the original feature functionality way too much to justify and we are worried it'll cause more bugs down the road. @johnstcn given that reasoning, would you be okay if we closed this and we can reopen the PR if we see a bigger need in the future? |
@f0ssel sure, this was just something I thought could be useful but nobody has asked for yet to the best of my knowledge |
At the very least, we need a mechanism (or something similar) that can report the status of various components in Coder. |
As an operator, I would like to be able to view the [health data from Coder] (#8971) in Prometheus:
Something like the below could be useful:
This will allow me to answer questions such as:
The text was updated successfully, but these errors were encountered: