Clayton Coleman 4e25a7951f Report container FS metrics into prometheus /metrics ... PerDiskStats reported from cgroups were not being surfaced into prometheus. In order to properly correlate the metrics, we need to assign a device label to each metric (which is the FS or device path). Since blkio cgroup tracks devices, we create a synthetic device `/dev/NAME` for the metric. Assign a Device label to each PerDiskStat for the handlers up front, and then surface the PerDiskStat values into the prometheus metrics. Report two new metrics - total bytes read and total bytes written.		2017-04-24 20:46:55 -04:00
..
test_resources	pull out common parts of docker and raw container handlers for use by rkt handler	2016-03-02 16:12:04 -08:00
container_hints_test.go	pull out common parts of docker and raw container handlers for use by rkt handler	2016-03-02 16:12:04 -08:00
container_hints.go	pull out common parts of docker and raw container handlers for use by rkt handler	2016-03-02 16:12:04 -08:00
fsHandler.go	Cadvisor now publishes per-container inode stats using the command 'find . -xdev printf '.'| wc -c' this is published in the v2 api using a new field	2016-10-12 13:16:21 -07:00
helpers.go	Report container FS metrics into prometheus /metrics	2017-04-24 20:46:55 -04:00
inotify_watcher.go	pull out common parts of docker and raw container handlers for use by rkt handler	2016-03-02 16:12:04 -08:00