-
Notifications
You must be signed in to change notification settings - Fork 18
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
Still got the dead Puma workers' metrics #8
Comments
Good point! We should somehow unset metrics for not existing processes. Or, better, not to include @dsalahutdinov, do you use |
Ah, now I can see that To fix it I will have to enhance Yabeda itself and Prometheus adapter for it to do metric aggregation. Related issues: yabeda-rb/yabeda#8 and yabeda-rb/yabeda-prometheus#10 That will take some time |
Please try yabeda-puma-plugin 0.6.0 with prometheus-client 2.1.0 or newer with direct file store set up. I believe that it should fix this. |
Hi,
I encountered an issue that I got the dead and live Puma workers' metrics together. I leveraged puma_worker_killer gem in my project, so it will kill one of worker periodically. How to get the live Puma workers' metrics only? Any work around? thanks.
Current processes
What I got from metrics
The text was updated successfully, but these errors were encountered: