Networking metrics

[dontrebootme]

Not sure how/where to make this request/suggestion, but network usage metrics may prove useful when collecting metrics on containers.

[discordianfish]

Hi,

you can try cadvisor which now has prometheus support, that includes network metrics. I don't think I'll add network metrics to the container_exporter but rather deprecate it in favor of cadvisor. The problem is that cadvisor doesn't support exposing the image name as label (yet).

[ZeroGraviti]

We have some limits in terms of number of container running per vm (e.g., openstack) like max 5 per node. We want to have the flexibility to provide a fallback option (just in case) if deploying a cadvisor container in a node pod is not possible. Along what lines do you propose I can proceed ? e.g., ip netns with iptables etc...

[jimmidyson]

@discordianfish cadvisor does expose the image name as a label now so if that's something you need then try out the latest cadvisor.

[aayllon]

Hi, I'm trying to use container_exporter with tsuru (http://docs.tsuru.io), our docker daemon api is exposed at tcp://0.0.0.0:2375, instead in a unix socket, I'm trying to run container_exporter with addr flag (./container_exporter -addr tcp://127.0.0.1:2375) but it return the error:

/var/run/docker.sock: connect: no such file or directory

There is any way to use container_exporter with a tcp socket?

[xbglowx]

@aayllon have you tried cAdvisor yet? I will be deprecating container-exporter in favor of that.