Docs » Configure application receivers » Configure application exporters and receivers for monitoring » cAdvisor

cAdvisor 🔗

Description 🔗

This receiver pulls metrics directly from cAdvisor, which runs by default on port 4194, but can be configured to any other port.

If you are using Kubernetes, consider the Kubelet Stats Receiver because many Kubernetes nodes do not expose cAdvisor on a network port, even though they are running it within Kubelet.

If you are running containers using Docker and the Docker Containers receiver, metrics duplication might happen, with the same metric data sent under different metric names. Consider not enabling the Docker Containers receiver in a Kubernetes environment, or use filtering to allow only certain metrics. Disabling the Docker Containers receiver causes the built-in Docker dashboards to be empty, though container metrics are available on the Kubernetes dashboards instead.

Benefits 🔗

After you configure the integration, you can access these features:

  • View metrics using the built-in dashboard. For information about dashboards, see View dashboards in Observability Cloud.

  • View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Splunk Infrastructure Monitoring navigators.

  • Access Metric Finder and search for metrics sent by the monitor. For information about Metric Finder, see Use the Metric Finder.

Installation 🔗

Follow these steps to deploy this integration:

  1. Follow the steps to deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:

  2. Configure the monitor, as described in the Configuration section.

  3. Restart the Splunk Distribution of OpenTelemetry Collector.

Configuration 🔗

This monitor is available in the Smart Agent Receiver, which is part of the Splunk Distribution of OpenTelemetry Collector. You can use existing Smart Agent monitors as OpenTelemetry Collector metric receivers with the Smart Agent Receiver.

This monitor requires a properly configured environment on your system, in which you’ve installed a functional Smart Agent release bundle. The Splunk Distribution of OpenTelemetry Collector provides this bundle in the installation paths for x86_64/amd64.

To activate this monitor in the Splunk Distribution of OpenTelemetry Collector, add the following lines to your configuration (YAML) file. See https://github.com/signalfx/splunk-otel-collector/tree/main/cmd/otelcol/config/collector on GitHub for the configuration (YAML) files.

receivers:
  smartagent/cadvisor: 
    type: cadvisor
    ... # Additional config

To complete the integration, include the receiver with this monitor type in a metrics pipeline. To do this, add the receiver to the service > pipelines > metrics > receivers section of your configuration file.

service:
  pipelines:
    metrics:
      receivers: [smartagent/cadvisor]

See the configuration example in GitHub for specific use cases that show how the Splunk OpenTelemetry Collector can integrate and complement existing environments.

Configuration settings 🔗

The following table shows the configuration options for this receiver:

Option

Required

Type

Description

cadvisor URL

no

string

Where to find cAdvisor. The default value is: http://localhost:4194.

Metrics 🔗

The following metrics are available for this integration:

Troubleshooting 🔗

If you are not able to see your data in Splunk Observability Cloud, try these tips:

To learn about even more support options, see Splunk Customer Success.