Skip to main content

New OpenTelemetry Network Protocol OpAMP - Game Changer for DevOps and Observability

Paul Stefanski
observIQ

Observability is one of the fastest growing industries in the world today — by both market size and data volume. Since the 90s, cloud monitoring has become a must-have for businesses in nearly every sector, not just technology. The exponentially increasing size of cloud infrastructures and data volume is creating two bubbles for customers seeking to collect and generate value from their data. Both are ready to burst. Both of these problems relate to how data collection agents are configured and managed, and new open source technologies by industry leaders are seeking to change the paradigm.

OpenTelemetry, a collaborative open source observability project, has introduced a new network protocol that addresses the infrastructure management headache, coupled with collector configuration options to filter and reduce data volume. Open Agent Management Protocol (OpAmp) is a new network protocol by the OpenTelemetry project that enables remote management of OpenTelemetry collectors (agents). In simple terms, it's a free and open source technology that dramatically reduces the effort and complexity of deploying and managing agents and data pipelines for DevOps teams.

Why is OpenTelemetry's OpAmp special?

It offers a simple and versatile method for remotely configuring and maintaining telemetry agents across massive environments with very little overhead. This is particularly useful for large cloud environments, and headless environments, where agent management would otherwise require manual management of every agent on every server.

OpAMP also enables agents to report information to multiple remote management destinations simultaneously, such as their status, properties, connections, configuration, operating system, version, agent CPU and RAM usage, data collection rate, and more. OpAMP can integrate with access credential management systems to keep environments secure. It also has a secure auto-update capability that makes maintaining large environments easy.

Similar technology is available through a handful of proprietary technologies, but the addition of OpAMP to OpenTelemetry is the launch point for industry-wide, vendor-agnostic adoption of the technology. Keeping with the open source mission, observability vendors collaborate on overarching technologies that benefit the whole industry, and focus independently on servicing specific niches.

That's what makes OpAMP so unique — as an open source technology built by experts from every major telemetry organization, it's completely vendor agnostic. It's available now as part of OpenTelemetry, but it's not dependent on OpenTelemetry as a whole.

OpAMP can be used to manage many agent types. Agents can collect data from any platform in any environment, and ship data to any, or multiple, data management or analysis platforms. Say you prefer a specific tool for data analysis, but another unrelated tool for data storage, and you also maintain an environment with servers across multiple cloud platforms; with OpAMP, you can manage different agent types across multiple environments through one place. Some agents, like OpenTelemetry agents, can ship to many analysis and storage tools simultaneously, and filter where specific data goes based on your configuration. With OpAMP, those agents and configurations are easily and remotely manageable at any scale, from source to destination.

OpenTelemetry is not meant to overrule or undercut any existing telemetry solutions. In fact it's exactly the opposite — it gives end users the freedom to use exactly the tools they want for their specific needs in conjunction with each other. As the observability industry continues to grow, and data volume swells, foundational technologies like OpAMP are critical to maintaining manageable technology infrastructures for both vendors and customers alike.

Paul Stefanski is Product Marketing Manager at observIQ

Hot Topics

The Latest

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

New OpenTelemetry Network Protocol OpAMP - Game Changer for DevOps and Observability

Paul Stefanski
observIQ

Observability is one of the fastest growing industries in the world today — by both market size and data volume. Since the 90s, cloud monitoring has become a must-have for businesses in nearly every sector, not just technology. The exponentially increasing size of cloud infrastructures and data volume is creating two bubbles for customers seeking to collect and generate value from their data. Both are ready to burst. Both of these problems relate to how data collection agents are configured and managed, and new open source technologies by industry leaders are seeking to change the paradigm.

OpenTelemetry, a collaborative open source observability project, has introduced a new network protocol that addresses the infrastructure management headache, coupled with collector configuration options to filter and reduce data volume. Open Agent Management Protocol (OpAmp) is a new network protocol by the OpenTelemetry project that enables remote management of OpenTelemetry collectors (agents). In simple terms, it's a free and open source technology that dramatically reduces the effort and complexity of deploying and managing agents and data pipelines for DevOps teams.

Why is OpenTelemetry's OpAmp special?

It offers a simple and versatile method for remotely configuring and maintaining telemetry agents across massive environments with very little overhead. This is particularly useful for large cloud environments, and headless environments, where agent management would otherwise require manual management of every agent on every server.

OpAMP also enables agents to report information to multiple remote management destinations simultaneously, such as their status, properties, connections, configuration, operating system, version, agent CPU and RAM usage, data collection rate, and more. OpAMP can integrate with access credential management systems to keep environments secure. It also has a secure auto-update capability that makes maintaining large environments easy.

Similar technology is available through a handful of proprietary technologies, but the addition of OpAMP to OpenTelemetry is the launch point for industry-wide, vendor-agnostic adoption of the technology. Keeping with the open source mission, observability vendors collaborate on overarching technologies that benefit the whole industry, and focus independently on servicing specific niches.

That's what makes OpAMP so unique — as an open source technology built by experts from every major telemetry organization, it's completely vendor agnostic. It's available now as part of OpenTelemetry, but it's not dependent on OpenTelemetry as a whole.

OpAMP can be used to manage many agent types. Agents can collect data from any platform in any environment, and ship data to any, or multiple, data management or analysis platforms. Say you prefer a specific tool for data analysis, but another unrelated tool for data storage, and you also maintain an environment with servers across multiple cloud platforms; with OpAMP, you can manage different agent types across multiple environments through one place. Some agents, like OpenTelemetry agents, can ship to many analysis and storage tools simultaneously, and filter where specific data goes based on your configuration. With OpAMP, those agents and configurations are easily and remotely manageable at any scale, from source to destination.

OpenTelemetry is not meant to overrule or undercut any existing telemetry solutions. In fact it's exactly the opposite — it gives end users the freedom to use exactly the tools they want for their specific needs in conjunction with each other. As the observability industry continues to grow, and data volume swells, foundational technologies like OpAMP are critical to maintaining manageable technology infrastructures for both vendors and customers alike.

Paul Stefanski is Product Marketing Manager at observIQ

Hot Topics

The Latest

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...