View OTel Collectors in Fleet

After you add OpenTelemetry (OTel) Collectors in Fleet, you can view them in the Agents list and open an individual collector to inspect its health, pipelines, metadata, and running configuration.

The Fleet → Agents page lists OTel Collectors alongside Elastic Agents. For each collector, the list shows its status, host name, CPU and memory usage (when internal telemetry is available), last activity timestamp, and version.

Two columns behave differently for collectors than for Elastic Agents:

• Agent policy shows a dash (-), because collectors use managed policies.
• Version shows the version the collector reports for itself (the same value as Service version on the details page), not an Elastic Stack version. An upstream OTel Collector reports its own release number, such as 0.144.0.

You can narrow the Agents list to only display OTel Collectors in two ways:

• From the Tags filter, select a tag. Every collector is automatically tagged with its service name, plus any tags you added when creating the collector group.
• From the Agent policies filter, select OpAMP. Fleet creates this managed policy automatically when you add your first collector, and enrolls every collector into it. The policy is hidden from the Agent policies tab, but you can still use it to filter the list.

Each collector is automatically tagged with its service name. This is the Service name you set when you added the collector, which defaults to a slug of the collector group display name, such as otel-collector-group. Elastic Agent running in OTel mode reports elastic-otel-collector. Any labels you enter in the Tags field are added as extra tags.

Collectors support a smaller set of actions than Elastic Agents. From the Actions menu on the collector's details page, or the actions menu in its row in the Agents list, you can select:

• View agent JSON: View the collector's stored details as JSON.
• Remove collector: Remove the collector from Fleet. Refer to Remove an OTel Collector from Fleet.

To open a collector, click its host name in the Agents list.

A collector also has a Logs tab, but it doesn't return data. To review a collector's logs, make sure internal telemetry is enabled and confirm the data is flowing in Kibana.

The Collector details tab shows the collector's pipelines as a graph, so you can see how telemetry flows from receivers through to exporters without reading the YAML.

The graph is built from the collector's effective configuration, so it renders even when the collector is offline.

Use the Pipeline selector to choose which pipelines to display:

• All pipelines displays every pipeline in the configuration.
• When a signal type has more than one pipeline, the selector includes an option for that signal, labeled with its pipeline count, such as All metrics (2 pipelines).
• Individual pipelines are listed last, by their configuration ID, such as logs, metrics, or metrics/host.

If the configuration defines no pipelines, the graph is replaced by a No pipelines configured message.

Each node is a pipeline component, labeled with its type and its configuration ID, and color-coded by type. The graph draws receivers, processors, exporters, and connectors. Extensions aren't drawn, because they don't participate in a pipeline.

The layout depends on your selection:

• When a single pipeline is displayed, components are laid out left to right in the order data flows through them.
• When several pipelines are displayed, each becomes a labeled container, with its components nested inside. A connector that exports from one pipeline and receives into another is drawn with a dashed line between the two containers.

When health data is available, each node shows a status indicator using the same states described in Check collector health. A pipeline container aggregates the health of the components inside it.

Use the zoom controls to zoom in, zoom out, or fit the graph to the panel. The graph refits automatically when you change the pipeline selection.

Click any node to open the component detail panel. Click it again, or click an empty area of the canvas, to close the panel.

A collector reports its own health and the health of each component in its pipelines. Where Fleet displays this depends on your version.

Clicking a component in the pipeline graph or in the Component health list opens a detail panel titled with the component's type and ID, such as Receiver: otlp. Its current health status appears in the panel header.

Depending on the selected component, the panel has up to three tabs.

This tab shows the component's reported health data.

This tab is available for receivers, processors, and exporters. It isn't available for connectors, or when you select a whole pipeline.

Metrics come from the collector's own telemetry, so this tab shows No metrics data available unless internal telemetry is enabled on the collector.

Select a time range of 5m, 15m, or 1h. Depending on the component type, up to three groups of charts are shown:

• Throughput (events/s): Rate of telemetry the component accepted or sent
• Errors (events/s): Rate of failed items
• Queue: Current queue size and capacity for exporters that queue data

This tab displays the component's own configuration as YAML, which you can copy. For receivers, processors, exporters, and connectors, a View component documentation link opens the upstream OpenTelemetry documentation for that component type.

When you select a whole pipeline, this tab shows the pipeline's wiring instead: its receivers, processors, and exporters.

The effective configuration is the configuration the collector is actually running. It can differ from the configuration file you wrote, because the collector resolves environment variables and merges multiple configuration sources.

The Error patterns table at the bottom of the Collector details tab groups similar error and warning messages from the collector's logs, so you can spot recurring problems without reading through every log line.

The table stays empty unless internal telemetry is enabled. When no matching messages exist, the table reports that no error patterns were found in the selected time range. Logs recorded before the collector is added in Fleet aren't included.

Use the controls to change what's shown:

• Select a time range of Last 5 minutes, Last 1 hour (the default), Last 1 day, or Last 1 week.
• Switch between Errors and Warnings. Errors covers the error and fatal log levels, and Warnings covers warn and warning.
• Sort by Most frequent or Most recent.

A summary next to the heading reports the number of patterns for the selected level, followed by the combined number of matching logs across both levels for the time range.

At most 20 patterns are returned for each level. For each pattern, the table shows its Level, the detected Pattern, its Count, First seen and Last seen timestamps, an Example message, and the Component that produced it. Click the icon in the last column to explore the matching logs in Discover.

• Monitor OpenTelemetry Collectors in Fleet
• Add an OTel Collector in Fleet
• Remove an OTel Collector from Fleet
• Add internal telemetry to an OTel Collector monitored by Fleet
• Troubleshoot OTel Collectors in Fleet