Open HappyFX opened 2 years ago
Related: #295
This seems to be a real problem. Whether we expose all metrics per namespace or just sum them up, we need to handle t his somehow.. @SuperQ wdyt?
+1 for @discordianfish
This sounds like a job for cAdvisor, not node_exporter.
@SuperQ The issue is, as I understand it, that we report the wrong numbers as soon as namespaces are used. While I don't want to get into the cAdvisor space, we can't just ignore that we're "missing" conntrack entries when monitoring reaching the node_nf_conntrack_entries_limit
Yes, I see that. But I'm not sure we'll be able to do anything about this in the node_exporter. Since this is done via network namespaces we would need to nsenter
each namespace to get the /proc/sys/net/netfilter/nf_conntrack_count
. I'm guessing this will require root, which we don't support.
@SuperQ Sure this is the only way? If so, I agree this is excessive..
When running with network namespaces counter in
/proc/sys/net/netfilter/nf_conntrack_count
showing correct value only for default namespace. Basic logic in linux kernelnode_nf_conntrack_entries_limit
limit is shared between all namespaces, but with node exporter we can get onlynf_conntrack_count
from default and we can't see the real sum of all network namespacenf_conntrack_count
in kernelHost operating system: output of
uname -a
Any linux host
node_exporter version: output of
node_exporter --version
node_exporter command line flags
Are you running node_exporter in Docker?
Yes
What did you do that produced an error?
Use namespaces in linux:
What did you expect to see?
What did you see instead?