-
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
[0.7.0-rc3] prometheus telemetry keep emitting data for stopped allocations #3474
Comments
Thanks for reporting this issue- a task shouldn't emit events when it is dead. We have added this to our near-term roadmap. |
personally i find it a pretty big bug, will make alerting etc seriously hard on the telemetry when stopped/dead allocations keep emitting the usage as if they are running, making 0.7 telemetry useless for cases like that :( i hope it can make it into 0.7-final considering this |
This bug is still present in 0.7.0 stable. |
Is this target for next 0.7.* release? |
@jippi Yep. PR is up |
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. |
this is a DatsDog chart using prometheus to show
nomad_client_allocs_memory_rss
grouped byalloc_id
- all those flat-lines are in fact allocations that is stopped, replaced by a new one (during a new submission of a job)I've verified those allocation IDs still exist in
/v1/metrics?format=prometheus
when when the allocation is stopped/deadTelemetry config:
The text was updated successfully, but these errors were encountered: