--- title: Operating OpenTelemetry at scale with OpAMP | daily.dev description: OpAMP (Open Agent Management Protocol) is a standardized protocol for remotely managing large fleets of observability agents, primarily OpenTelemetry... canonical: https://daily.dev/posts/operating-opentelemetry-at-scale-with-opamp-3usspxenc twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Operating OpenTelemetry at scale with OpAMP | daily.dev og:description: OpAMP (Open Agent Management Protocol) is a standardized protocol for remotely managing large fleets of observability agents, primarily OpenTelemetry... og:url: https://daily.dev/posts/operating-opentelemetry-at-scale-with-opamp-3usspxenc og:image: https://api.daily.dev/og/posts/3UssPxenc.png og:image:alt: Operating OpenTelemetry at scale with OpAMP og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Operating OpenTelemetry at scale with OpAMP **[CNCF](https://daily.dev/sources/cncf)** · 8 min read · 0 upvotes · 0 comments ## Summary OpAMP (Open Agent Management Protocol) is a standardized protocol for remotely managing large fleets of observability agents, primarily OpenTelemetry Collectors. It enables central backends to push configuration updates, monitor agent health, and collect status information over WebSocket or HTTP. The protocol uses just two protobuf messages and supports an extension model (read-only) and a supervisor model (read-write with safe rollback). Beyond OTel Collectors, OpAMP can manage Kubernetes deployments via an OpAMP Bridge, Java SDKs for hot-reloading config, and Fluent Bit agents. A newly launched OpAMP Gateway Extension addresses WebSocket connection scaling limits by acting as a multiplexer — allowing 100,000 collectors to connect through 100 gateways rather than directly to the management platform. The project is currently in beta, with roadmap items including config diff support, true hot-reloading, and a telemetry policy OTEP that separates intent from implementation. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is OpAMP and how does it manage OpenTelemetry Collector fleets? OpAMP (Open Agent Management Protocol) is a standardized protocol under the OpenTelemetry project that lets a central backend remotely configure agents, push updates, monitor health, and collect status from fleets of collectors over WebSocket or HTTP. It uses just two Protocol Buffers messages, server-to-agent and agent-to-server, and works via an OpAMP extension for reporting and a supervisor process for applying config changes. _Teams standardizing collector fleet management can track OpAMP developments alongside other observability tooling on daily.dev._ ### How does the OpAMP supervisor safely apply new configuration to an OpenTelemetry Collector without breaking telemetry pipelines? The supervisor writes the new configuration to disk, shuts down the collector, and restarts it with that configuration. If the collector fails to start, the supervisor automatically reverts to the last known good configuration, preventing a bad remote config push from breaking telemetry pipelines in production. _Anyone rolling out remote config changes to observability agents can keep an eye on safety patterns like this via daily.dev._ ### What is the OpAMP Gateway Extension and what problem does it solve for large collector deployments? The OpAMP Gateway Extension is an alpha OpenTelemetry Collector extension launched around KubeCon Europe 2026 that acts as a multiplexer for OpAMP control-plane connections, aggregating messages from thousands of edge collectors and relaying them through fewer upstream connections. It solves WebSocket connection limits at scale, for example turning 100,000 direct collector connections into 100 gateway connections to the management platform, each handling 1,000 collectors, and also supports network-segmented environments. _Engineers scaling collector fleets into the thousands can follow gateway-style solutions like this on daily.dev._ ## Similar posts on daily.dev - [Why should you demand OpAMP support from your vendor?](https://daily.dev/posts/why-should-you-demand-opamp-support-from-your-vendor--g4ds6vjqb) · Coralogix · 0 upvotes · 0 comments - [Managing OpenTelemetry at Scale: Why OTel Pipelines Need a Control Plane](https://daily.dev/posts/managing-opentelemetry-at-scale-why-otel-pipelines-need-a-control-plane-7xcortcs0) · Coralogix · 0 upvotes · 0 comments --- Tags: [#observability](https://daily.dev/tags/observability), [#distributed-systems](https://daily.dev/tags/distributed-systems), [#opentelemetry](https://daily.dev/tags/opentelemetry) [View this post on daily.dev](https://daily.dev/posts/operating-opentelemetry-at-scale-with-opamp-3usspxenc) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Operating OpenTelemetry at scale with OpAMP","url":"https://daily.dev/posts/operating-opentelemetry-at-scale-with-opamp-3usspxenc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/operating-opentelemetry-at-scale-with-opamp-3usspxenc"},"datePublished":"2026-07-13T11:33:15.067Z","dateModified":"2026-09-13T19:14:59.631Z","description":"OpAMP (Open Agent Management Protocol) is a standardized protocol for remotely managing large fleets of observability agents, primarily OpenTelemetry...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/46c579a9462927556bb50b0fd26b588d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/46c579a9462927556bb50b0fd26b588d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"CNCF","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"CNCF","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/55536a03390741eebd96d2f9b74d2d8d","url":"https://daily.dev/sources/cncf"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/operating-opentelemetry-at-scale-with-opamp-3usspxenc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"observability,distributed-systems,opentelemetry","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"CNCF","item":"https://daily.dev/sources/cncf"},{"@type":"ListItem","position":3,"name":"Operating OpenTelemetry at scale with OpAMP"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/operating-opentelemetry-at-scale-with-opamp-3usspxenc#faq","mainEntity":[{"@type":"Question","name":"What is OpAMP and how does it manage OpenTelemetry Collector fleets?","acceptedAnswer":{"@type":"Answer","text":"OpAMP (Open Agent Management Protocol) is a standardized protocol under the OpenTelemetry project that lets a central backend remotely configure agents, push updates, monitor health, and collect status from fleets of collectors over WebSocket or HTTP. It uses just two Protocol Buffers messages, server-to-agent and agent-to-server, and works via an OpAMP extension for reporting and a supervisor process for applying config changes. Teams standardizing collector fleet management can track OpAMP developments alongside other observability tooling on daily.dev."}},{"@type":"Question","name":"How does the OpAMP supervisor safely apply new configuration to an OpenTelemetry Collector without breaking telemetry pipelines?","acceptedAnswer":{"@type":"Answer","text":"The supervisor writes the new configuration to disk, shuts down the collector, and restarts it with that configuration. If the collector fails to start, the supervisor automatically reverts to the last known good configuration, preventing a bad remote config push from breaking telemetry pipelines in production. Anyone rolling out remote config changes to observability agents can keep an eye on safety patterns like this via daily.dev."}},{"@type":"Question","name":"What is the OpAMP Gateway Extension and what problem does it solve for large collector deployments?","acceptedAnswer":{"@type":"Answer","text":"The OpAMP Gateway Extension is an alpha OpenTelemetry Collector extension launched around KubeCon Europe 2026 that acts as a multiplexer for OpAMP control-plane connections, aggregating messages from thousands of edge collectors and relaying them through fewer upstream connections. It solves WebSocket connection limits at scale, for example turning 100,000 direct collector connections into 100 gateway connections to the management platform, each handling 1,000 collectors, and also supports network-segmented environments. Engineers scaling collector fleets into the thousands can follow gateway-style solutions like this on daily.dev."}}]} ```