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 upIntroduce metric for per-exporter pressure on prometheus itself #1755
Comments
This comment has been minimized.
This comment has been minimized.
|
What you're mostly looking for is the number of samples that an exporter is producing. Usually it's just a handful of metrics in one exporter. http://www.robustperception.io/which-are-my-biggest-metrics/ |
fabxc
added
the
kind/question
label
Jun 21, 2016
This comment has been minimized.
This comment has been minimized.
|
You can also do something along the lines of:
That can be expensive though. |
This comment has been minimized.
This comment has been minimized.
|
Thanks, that looks useful. However:
I'll see if I can do something to get the information out of prom. |
This comment has been minimized.
This comment has been minimized.
|
|
brian-brazil
closed this
Feb 13, 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.
harmw commentedJun 21, 2016
Is it possible to expose some kind of metric to point out the amount of stress a certain metrics endpoint poses on the prometheus machine itself? We have several exporters in our platform, just no simple way of figuring out which one of those is stressing prometheus the most. Some more insights in this process would be great.