-
Notifications
You must be signed in to change notification settings - Fork 151
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 health check endpoint for the collector #145
Comments
What collectors are you running?
…On Fri, 4 Dec 2020 at 1:26 am, kubibektas ***@***.***> wrote:
hi,
we are using metrics collector as a centralized Kubernetes pod that
receives metrics from all the application pods. As we have more metrics,
the collector pod (metrics server) stops functioning properly and we get ruby_collector_working
0. We noticed the pod was getting CPU throttled and increased the
resources for it but would it be possible to add a health check endpoint
so that Kubernetes would detect it automatically and restart the pod
through a liveness probe?
I saw there was a closed issue for the same feature (#69
<#69>) But wanted
to raise it again as it seems to be a useful functionality.
Thanks you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#145>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAABIXIMT3PWO445UTQGS43SS6N2LANCNFSM4UMBTEGQ>
.
|
Hi Sam, thanks for the response. We are just running server as |
We would also like to have this feature 👍 |
I am open to have a PR that adds a trivial health check at so |
hi,
we are using metrics collector as a centralized Kubernetes pod that receives metrics from all the application pods. As we have more metrics, the collector pod (metrics server) stops functioning properly and we get
ruby_collector_working 0
. We noticed the pod was getting CPU throttled and increased the resources for it but would it be possible to add ahealth check
endpoint so that Kubernetes would detect it automatically and restart the pod through a liveness probe?I saw there was a closed issue for the same feature (#69) But wanted to raise it again as it seems to be a useful functionality.
Thanks you!
The text was updated successfully, but these errors were encountered: