Manage OpenTelemetry agents and collectors in UI

Learn about the Fleet Management user interface.

The Fleet Management page provides a centralized dashboard to track the status, version, and effective configuration of OpenTelemetry collectors and instrumentation agents across your environment.

It provides the following benefits:

  • Enhanced visibility: Gain clear insights into telemetry pipeline health and configuration state, significantly reducing the time required to diagnose collector-related issues.

  • Rapid identification: Quickly identify and resolve issues with misconfigured, disconnected, or outdated agents.

Prerequisite

Ensure to configure OpAMP for collector and agents. See Set up OpenTelemetry Fleet Management.

Supported clients

  • Splunk distribution of OpenTelemetry Collector (Agent and Gateway modes) 0.154.0 or later.

  • Splunk distribution of OpenTelemetry Java agent 2.29.0 or later

  • Splunk Distribution of OpenTelemetry Node.js agent 4.8.0 or later

Configuration for viewing the environment names for collectors and agents

If you are using Splunk distribution of OpenTelemetry Collector prior to the version 0.154.0, specify the following attributes in the agent_config.yaml file:

CODE 
collector:
    config:
      extensions:
        opamp:
          # existing config...
          agent_description:
            include_resource_attributes: true
      service:
        telemetry:
          resource:
            k8s.cluster.name: <your-cluster-name>
            deployment.environment.name: <your-environment>
            otelcol.service.mode: gateway

Adding the attributes enables you to view the environment on which the collectors and the agents are deployed.

Note: In version 0.154.0, the collector does not include the deployment.environment.name attribute by default. You must manually add this attribute.