Skip to content
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

Closed
neelance opened this issue Mar 25, 2015 · 8 comments
Closed

filter for node_filesystem_* and node_network_* #60

neelance opened this issue Mar 25, 2015 · 8 comments

Comments

@neelance
Copy link

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/*"} and node_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?

@brian-brazil
Copy link
Contributor

There's already a --collector.filesystem.ignored-mount-points for the former and we'd accept a PR to add similar for the latter.

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.

@neelance
Copy link
Author

No, most of the filesystems and devices don't exist any more.

@juliusv
Copy link
Member

juliusv commented Mar 25, 2015

@neelance Ok, so they don't exist on the host anymore, but you can still see them on your node exporter's /metrics HTTP endpoint (could you confirm)? In that case, it's indeed a bug that should be fixed in the node exporter.

@neelance
Copy link
Author

Yes, exactly.

@juliusv
Copy link
Member

juliusv commented Mar 25, 2015

@neelance Thanks, I opened #61 to track this then. Closing this one then (please reopen if you feel like there's something missing).

@juliusv juliusv closed this as completed Mar 25, 2015
@neelance
Copy link
Author

What about the network interfaces? Shouldn't it also drop those when they don't exist any more?

@juliusv
Copy link
Member

juliusv commented Mar 25, 2015

@neelance Ah thanks, I missed that second part. Filed an issue about that too: #62

@neelance
Copy link
Author

Great, thanks!

rphillips pushed a commit to rphillips/node_exporter that referenced this issue Mar 17, 2020
Bug 1803058: text_collectors: Don't detect AWS twice when virt-what is upgraded
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants