How does cAdvisor collect the data?

[kant kodali]

Below is paragraph I got from the cAdvisor documentation and I would like to know little bit more about how it collects the resource usage? is it simply a running daemon that does "ps aux" or in general just executes some shell commands and captures all the data? what if the daemon crashes? if we were deploy this on production along with our App we should also plan for its consumption of resource usage and other potential issues it could cause right?

"cAdvisor (Container Advisor) provides container users an understanding of the resource usage and performance characteristics of their running containers. It is a running daemon that collects, aggregates, processes, and exports information about running containers. Specifically, for each container it keeps resource isolation parameters, historical resource usage, histograms of complete historical resource usage and network statistics. This data is exported by container and machine-wide"

[Vishnu Kannan]

cAdvisor is designed to monitor multiple containers at a time. Typically, you'd run one cAdvisor instance per node. cAdvisor uses kernel APIs like cgroups, vfs, procfs, sysfs, etc., to collect metrics. 

Resource usage of cAdvisor is something that is being continuously optimized over time. We have not heard any issues from existing users about resource usage of cAdvisor.

On Fri, Apr 29, 2016 at 11:08 AM, kant kodali <kant...@gmail.com> wrote:

Below is paragraph I got from the cAdvisor documentation and I would like to know little bit more about how it collects the resource usage? is it simply a running daemon that does "ps aux" or in general just executes some shell commands and captures all the data? what if the daemon crashes? if we were deploy this on production along with our App we should also plan for its consumption of resource usage and other potential issues it could cause right?

"cAdvisor (Container Advisor) provides container users an understanding of the resource usage and performance characteristics of their running containers. It is a running daemon that collects, aggregates, processes, and exports information about running containers. Specifically, for each container it keeps resource isolation parameters, historical resource usage, histograms of complete historical resource usage and network statistics. This data is exported by container and machine-wide"

--
You received this message because you are subscribed to the Google Groups "Containers at Google" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-contain...@googlegroups.com.
To post to this group, send email to google-c...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-containers.
For more options, visit https://groups.google.com/d/optout.