← sources

Centrally Managing OTel Collectors with Elastic Agent and Fleet

source: reddit (reddit:devops)published 2026-08-26 17:12ingested 2026-08-27 13:02

retained text

<table> <tr><td> <a href="https://www.reddit.com/r/devops/comments/1vz38io/centrally_managing_otel_collectors_with_elastic/"> <img alt="Centrally Managing OTel Collectors with Elastic Agent and Fleet" src="https://external-preview.redd.it/P_i46wEzjNwyu4MU1GDHC7liFEkemXWlVNuc3ajRIB8.jpeg?width=640&amp;crop=smart&amp;auto=webp&amp;s=56b84bfa12761563f508b2890e74aa36f237c1df" title="Centrally Managing OTel Collectors with Elastic Agent and Fleet" /> </a> </td><td> <!-- SC_OFF --><div class="md"><p>Managing OpenTelemetry collectors at scale has been a pain point for a while now. You either run standalone collectors and lose central visibility, or you build custom tooling to keep configs in sync across environments. This takes a different approach by embedding an OTel Collector directly into the agent, so you get Fleet-based central management for both your existing Beats integrations and native OTel pipelines in the same process.</p> </div><!-- SC_ON --> &#32; submitted by &#32; <a href="https://www.reddit.com/user/AvenueJay"> /u/AvenueJay </a> <br /> <span><a href="https://www.elastic.co/observability-labs/blog/centrally-managed-otel-collectors-with-elastic-fleet">[link]</a></span> &#32; <span><a href="https://www.reddit.com/r/devops/comments/1vz38io/centrally_managing_otel_collectors_with_elastic/">[comments]</a></span> </td></tr></table>

document fetched 2026-08-27 13:02 · canonical https://reddit.com/r/devops/comments/1vz38io/centrally_managing_otel_collectors_with_elastic