-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
filter for node_filesystem_* and node_network_* #60
Comments
There's already a Do these filesystems and devices still exist? If not, that's a bug in the node_exporter as it should only be exporting things that exist right now. |
No, most of the filesystems and devices don't exist any more. |
@neelance Ok, so they don't exist on the host anymore, but you can still see them on your node exporter's |
Yes, exactly. |
What about the network interfaces? Shouldn't it also drop those when they don't exist any more? |
Great, thanks! |
Bug 1803058: text_collectors: Don't detect AWS twice when virt-what is upgraded
We're running node_exporter on machines on which we use Docker. There are a lot of docker containers that get spawned and destroyed. Over time, node_exporter accumulates hundreds of entries for
node_filesystem_*{filesystem="/var/lib/docker/devicemapper/mnt/*"}
andnode_network_*{device="veth*"}
. I think that could be a reason why our prometheus is using a lot of memory. I see two possible solutions: One is to filter those values completely, the other is to forget about old entries after some time. What do you think?The text was updated successfully, but these errors were encountered: