node_exporter
node_exporter copied to clipboard
Replace netstat parsers with procfs netstat parsers
Replace this parsers in node exporter with this ones from procfs.
@discordianfish Can you please assign this to me, i will start working on it asap.
@discordianfish @SuperQ I think we should consider refactoring the types of the metrics on the procfs side here, here and here from float64
to *float64
because we need to have a value only for the metrics provided by the current system. And afterwards check on the node_exporter side here if the value is not nil
and feed it to the channel.
What do you think about this?
I think this is reasonable
Any progress on getting this resolved?
@jcpunk Yes, I will work on it during the next days.
Hey @nikakis, any chance I can take this issue? I would like to give this a shot.
Go for it.
hi, i've been exploring and using prometheus exporters as of late and would love to contribute some fixes etc to this project (learning stuff along the way). I think no one's actively working on this issue right now and would like to take this up.
I have a question about this issue tho: I've looked into the relevant parts of both the codebases and read up about the proc
filesystem and it seems like the mentioned prometheus/procfs netstat parsers currently require a PID and are process specific, as in they're only made to parse /proc/<pid>/net/netstat
and not the overall /proc/net/netstat
which is what the node_exporter currently uses. And I think these two can vary if the process is in a different network namespace?
p.s. this is my first time learning about these concepts and contributing to Golang / cloud projects in general so there are chances I might've missed something