Monitor OpenTelemetry Collectors in Fleet
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Preview
Preview
Stack
Preview
9.4+
Preview since 9.4
Use Fleet to centrally monitor Elastic Agent 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
- Elastic Agent: version 9.2 or later
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.
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability Preview This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Preview since 9.5 This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Collectors get a dedicated details page in Fleet, with a pipeline visualization and panels for health, metadata, configuration, and recurring errors in the collector's logs.
Learn more: