Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upprometheus_targetpool_duration_ms should be labeled by job, not by interval now #324
Comments
This comment has been minimized.
This comment has been minimized.
|
This is obsolete. We now have target_interval_length_seconds broken out by interval. The primary use case of this is detecting overload in Prometheus itself, so breaking out by interval is sufficient. |
juliusv
closed this
Jan 2, 2015
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
juliusv commentedJun 28, 2013
...since targetpools are now keyed by job and that's probably a more interesting dimension anyways.