# Why was cAdvisor replaced with Docker stats?

**URL:** <https://forums.suse.com/t/why-was-cadvisor-replaced-with-docker-stats/4791>\
**Category:** Rancher 1.x\
**Created:** [December 3, 2016, 7:20pm UTC](https://forums.suse.com/t/why-was-cadvisor-replaced-with-docker-stats/4791 "2016-12-03T19:20:30Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmreicha](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/jmreicha/32/444_2.png) [@jmreicha](https://forums.suse.com/u/jmreicha)\
**Post date:** [December 3, 2016, 7:20pm UTC](https://forums.suse.com/t/why-was-cadvisor-replaced-with-docker-stats/4791/1 "2016-12-03T19:20:30Z")

</div>

I noticed in the 1.2 release notes that cAdvisor has been replaced by Docker stats, can somebody explain why this decision was made? I don’t have an issue with the switch, just curious why the decision was made.

---

<div class="post-metadata">

**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\
**Post date:** [December 3, 2016, 8:06pm UTC](https://forums.suse.com/t/why-was-cadvisor-replaced-with-docker-stats/4791/2 "2016-12-03T20:06:47Z")

</div>

cAdvisor collects data all the time when nobody is looking at it 99% of the time, and expends a considerable amount of effort doing so with things like running `du` every update. Also [lack of] Windows support.

---

<div class="post-metadata">

**Author:** ![jmreicha](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/jmreicha/32/444_2.png) [@jmreicha](https://forums.suse.com/u/jmreicha)\
**Post date:** [December 3, 2016, 8:48pm UTC](https://forums.suse.com/t/why-was-cadvisor-replaced-with-docker-stats/4791/3 "2016-12-03T20:48:12Z")

</div>

Interesting. Thanks for the info!

---

<div class="post-metadata">

**Author:** ![Animesh](https://avatars.discourse-cdn.com/v4/letter/a/5e9695/32.png) [@Animesh](https://forums.suse.com/u/Animesh)\
**Post date:** [February 28, 2017, 10:43am UTC](https://forums.suse.com/t/why-was-cadvisor-replaced-with-docker-stats/4791/4 "2017-02-28T10:43:34Z")

</div>

You can face another issue with cAdvisor which is quite frequent. As Vincent explained it keeps watching the container mount space all the time. This throws error when you try to remove the container as mount space has been leaked and being used by cAdvisor. You can see below error quite frequently-

> Error response from daemon: Unable to remove filesystem for : remove /var/lib/docker/containers//shm: device or resource busy