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 upAdd counter for prometheus query engine queries #4334
Comments
This comment has been minimized.
This comment has been minimized.
|
prometheus_engine_query_duration_seconds_count already covers this. |
This comment has been minimized.
This comment has been minimized.
|
Ah, thank you. Sorry didn't see that before. |
d-shi
closed this
Jul 3, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 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 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
d-shi commentedJul 2, 2018
Proposal
Similar to #2325, but add one additional metric that is a counter for number of queries coming in to prometheus query engine. Right now there is a metric called
prometheus_engine_queries, which is a gauge. We see that most of the time this gauge has a value of 0 (sometimes one data point will be 1).We are trying to debug why
prometheus_engine_query_duration_secondslatencies spike up to >10 seconds sometimes, and would like to know if it correlates to a massive number of queries coming in, but do not have this metric currently since the gauge is mostly 0 (so at least no real queuing of queries is happening).