-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Nomad Metrics don't match Telemetry documentation #4126
Comments
Hey the "nomad.client.allocs" are emitted metrics: https://github.com/hashicorp/nomad/blob/master/client/alloc_runner.go#L774 I have also made a PR to fix the uptime metric as that was a mistake. If you see any other mismatched metrics please let us know. |
Just to clarify that the |
Thanks for the clarifications guys. @schmichael I have allocations already running but I have a question though. If any allocation has failed ever then nomad would emit Thanks for your time! |
Yes. That metric is a counter, so it will increment with each allocation failure on a client node until that client node's Nomad process is restarted. Even if the failed allocations are garbage collected the counter will not reset until the process exits. Hope that helps! |
Yeah thats enough! Thanks for the quick responses guys. Keep up the good work! |
I didnt understand about the "nomad.client.allocs" are emitted metrics. Basically my objective is to get the data if any of my job is restarting or in a failed state. I am using Prometheus capturing data from nomad telemetry. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Nomad v0.7.1 (0b295d399d00199cfab4621566babd25987ba06e)
Operating system and Environment details
Issue
Metrics received by the nomad api don't match the official telemetry documentation.
Reproduction steps
Following with the prior reference to the official documentation, lets take for example
nomad.client.allocs.*
. I query the nomad API and I get nothing:However, if I query asking for nomad.clients.allocations, I get the following:
Another example could be
nomad.client.uptime
which doesn't exist, instead I havenomad.uptime
.Here is the whole list of
nomad.client
metrics:The text was updated successfully, but these errors were encountered: