Go to file
Vishnu kannan 7f6127620a Link cAdvisor statically.
Signed-off-by: Vishnu kannan <vishnuk@google.com>
2016-05-20 13:39:13 -07:00
api Make manager multi-container functions robust to partial failures 2016-05-16 13:25:33 -07:00
build Link cAdvisor statically. 2016-05-20 13:39:13 -07:00
cache re-order the import package 2015-11-30 16:43:22 +08:00
client Fix out of date client/README.md 2016-02-08 13:54:55 -08:00
collector Add a flag to control the number of custom metrics scraped by collectors 2016-02-11 01:33:58 +01:00
container Merge pull request #1204 from pmorie/dm-support 2016-05-18 12:30:05 -07:00
deploy fixed ldconfigs glibc path 2016-02-23 19:38:19 +01:00
devicemapper Add devicemapper support for docker containers 2016-05-18 15:19:20 -04:00
docs Add link to cAdvisor release instructions 2016-05-12 16:02:45 -07:00
events Don't create a EventStore if the event limit is set to 0 2016-04-25 16:50:17 -07:00
fs Add devicemapper support for docker containers 2016-05-18 15:19:20 -04:00
Godeps Polling rkt implementation of new watcher inteface (#1284) 2016-05-17 10:34:56 -07:00
healthz Fix imported package names to not use mixedCaps or under_scores 2015-10-22 12:10:57 +08:00
http re-order the import package 2015-11-30 16:43:22 +08:00
info Move docker types to v1 API 2016-05-02 15:52:29 -07:00
integration Add devicemapper support for docker containers 2016-05-18 15:19:20 -04:00
machine Move utils/machine -> machine 2016-05-02 15:56:49 -07:00
manager Fix nil-interface partialFailure bug 2016-05-19 16:16:58 -07:00
metrics add cgroup quota and period support / add missing tests 2016-02-02 20:33:11 +01:00
pages Added per-subcontainer charts to the UI. 2016-05-10 14:23:32 -07:00
storage add optional TLS client auth to Kafka storage 2016-05-06 15:40:29 -05:00
summary Export type to calculate percentiles 2015-07-21 17:52:01 -07:00
utils Merge pull request #1292 from timstclair/tail 2016-05-19 12:16:24 -07:00
validate Don't validate docker state file, since it's no longer used 2016-05-06 19:29:24 -07:00
version Release v0.23.2 2016-05-18 15:20:31 -07:00
.gitignore git ignore test binaries 2016-04-04 15:46:25 -07:00
.travis.yml Update golang to v1.5.3 2016-01-21 14:57:18 -08:00
AUTHORS Remove mention of contributors file. We don't have one. 2014-12-30 17:16:46 +00:00
cadvisor_test.go Fixes for --disable_metrics flag 2016-05-02 22:47:37 -07:00
cadvisor.go Inline storageDriver usage & fix error message 2016-05-05 17:13:41 -07:00
CHANGELOG.md Release v0.23.2 2016-05-18 15:20:31 -07:00
CONTRIBUTING.md Add CONTRIBUTING.md 2014-06-10 13:09:14 -07:00
LICENSE Migrating cAdvisor code from lmctfy 2014-06-09 12:12:07 -07:00
logo.png Run PNG crusher on logo.png 2016-02-10 15:02:44 -08:00
Makefile Separated asset files into their own folder with the correct file 2016-04-21 15:16:08 -07:00
README.md Cleanup cAdvisor storage docs 2016-05-04 19:41:07 -07:00
storagedriver.go Inline storageDriver usage & fix error message 2016-05-05 17:13:41 -07:00
test.htdigest Added HTTP Auth and HTTP Digest authentication #302 2014-12-11 17:25:43 +05:30
test.htpasswd Added HTTP Auth and HTTP Digest authentication #302 2014-12-11 17:25:43 +05:30

cAdvisor

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.

cAdvisor has native support for Docker containers and should support just about any other container type out of the box. We strive for support across the board so feel free to open an issue if that is not the case. cAdvisor's container abstraction is based on lmctfy's so containers are inherently nested hierarchically.

cAdvisor

Quick Start: Running cAdvisor in a Docker Container

To quickly tryout cAdvisor on your machine with Docker, we have a Docker image that includes everything you need to get started. You can run a single cAdvisor to monitor the whole machine. Simply run:

sudo docker run \
  --volume=/:/rootfs:ro \
  --volume=/var/run:/var/run:rw \
  --volume=/sys:/sys:ro \
  --volume=/var/lib/docker/:/var/lib/docker:ro \
  --publish=8080:8080 \
  --detach=true \
  --name=cadvisor \
  google/cadvisor:latest

cAdvisor is now running (in the background) on http://localhost:8080. The setup includes directories with Docker state cAdvisor needs to observe.

Note: If you're running on CentOS, Fedora, RHEL, or are using LXC take a look at our running instructions.

We have detailed instructions on running cAdvisor standalone outside of Docker. cAdvisor running options may also be interesting for advanced usecases. If you want to build your own cAdvisor Docker image see our deployment page.

Building and Testing

See the more detailed instructions in the build page. This includes instructions for building and deploying the cAdvisor Docker image.

Exporting stats

cAdvisor supports exporting stats to various storage plugins. See the documentation for more details and examples.

Web UI

cAdvisor exposes a web UI at its port:

http://<hostname>:<port>/

See the documentation for more details.

Remote REST API & Clients

cAdvisor exposes its raw and processed stats via a versioned remote REST API. See the API's documentation for more information.

There is also an official Go client implementation in the client directory. See the documentation for more information.

Roadmap

cAdvisor aims to improve the resource usage and performance characteristics of running containers. Today, we gather and expose this information to users. In our roadmap:

  • Advise on the performance of a container (e.g.: when it is being negatively affected by another, when it is not receiving the resources it requires, etc)
  • Auto-tune the performance of the container based on previous advise.
  • Provide usage prediction to cluster schedulers and orchestration layers.

Community

Contributions, questions, and comments are all welcomed and encouraged! cAdvisor developers hang out on Freenode IRC in the #google-containers room & Slack (get an invitation here). We also have the google-containers Google Groups mailing list.