Understanding the metrics component of DC/OS

The metrics component provides metrics from DC/OS cluster hosts, containers running on those hosts, and from applications running on DC/OS that send StatsD metrics to the Mesos Metrics Module. The metrics component is natively integrated with DC/OS and is available per-host from the /system/v1/metrics/v0 HTTP API endpoint.


DC/OS provides these types of metrics:

  • Host: - Metrics about the specific node which is part of the DC/OS cluster.
  • Container: - Metrics about cgroup allocations from tasks running in the DC/OS Universal Container Runtime or Docker Engine runtime.
  • Application: - Metrics about a specific application running inside the Universal Container Runtime.

The Metrics API exposes these areas.

The DC/OS metrics component produces Prometheus metrics on port 61091, eliminating the need to run the Prometheus plugin supported by previous versions of DC/OS.

All three metrics layers are aggregated by a collector which is shipped as part of the DC/OS distribution. This enables metrics to run on every host in the cluster. It is the main entry point to the metrics ecosystem, aggregating metrics sent to it by the Mesos Metrics module, or gathering host and container level metrics on the machine on which it runs.

The Mesos Metrics module is bundled with every agent in the cluster. This module enables applications running on top of DC/OS to publish metrics to the collector by exposing StatsD host and port environment variables inside every container. These metrics are appended with structured data such as agent-id, framework-id, and task-id. DC/OS applications discover the endpoint via an environment variable (STATSD_UDP_HOST or STATSD_UDP_PORT). Applications leverage this StatsD interface to send custom profiling metrics to the system.

For more information on which metrics are collected, see the Metrics Reference.