---
title: Monitor OpenTelemetry Collectors in Fleet
description: Centrally monitor EDOT and OpenTelemetry Collectors in Fleet using OpAMP.
url: https://www.elastic.co/elastic/docs-builder/docs/3364/reference/fleet/monitor-otel-collectors
products:
  - Elastic Agent
  - Fleet
applies_to:
  - Elastic Cloud Serverless: Preview
  - Elastic Stack: Preview since 9.4
---

# Monitor OpenTelemetry Collectors in Fleet
Use Fleet to centrally monitor Elastic Distribution of OpenTelemetry (EDOT) Collectors and third-party OpenTelemetry (OTel) Collectors running in your infrastructure. Fleet provides visibility into the health, configuration, and telemetry of any OTel Collector with the OpAMP extension, so you can troubleshoot issues, plan capacity, and monitor operations from a single interface.
For monitoring OTel Collectors, Fleet uses the Open Agent Management Protocol (OpAMP). Collectors report their status and configuration to Fleet Server, which acts as an OpAMP server. Fleet doesn't deploy OTel Collectors — you install and run them separately, then configure them with the OpAMP extension to report to Fleet Server.
Supported collectors:
- OpenTelemetry Collector (upstream and community-contributed distributions): version 0.103.0 or later
- EDOT Collector: version 9.2 or later

<note>
  Unlike Elastic Agents, OTel Collectors don't display an agent policy in the **Agents** list. They use managed policies that can't be modified and aren't displayed in the **Agent policies** tab.
</note>

Learn more:
- [Add an OTel Collector in Fleet](https://www.elastic.co/elastic/docs-builder/docs/3364/reference/fleet/add-otel-collector)
- [View OTel Collectors in Fleet](https://www.elastic.co/elastic/docs-builder/docs/3364/reference/fleet/view-otel-collectors)
- [Add internal telemetry to an OTel Collector monitored by Fleet](https://www.elastic.co/elastic/docs-builder/docs/3364/reference/fleet/add-otel-collector-internal-telemetry)