Skip to main content

New EMA Report: OpenTelemetry's Emerging Role in IT Performance and Availability

Pete Goldin
APMdigest

OpenTelemetry is quickly becoming a foundational element of observability, according to a new report I wrote in partnership with Dan Twing, President and COO of Enterprise Management Associates (EMA), titled Taking Observability to the Next Level: OpenTelemetry's Emerging Role in IT Performance and Reliability. The report was sponsored by Elastic, an APMdigest sponsor, as well as Apica, Beta Systems, Dynatrace, Embrace and SolarWinds.

WEBINAR APRIL 15: Unlocking the Future of Observability: OpenTelemetry’s Role in IT Performance and Innovation

OpenTelemetry (OTel) is an open source CNCF project offering a framework and suite of tools including APIs and SDKs that facilitate the generation, collection, and exporting of telemetry data for observability platforms and related tools. OTel collects logs, metrics and traces, and is expanding data types to include profiling and many other possibilities.

This report comes at just the right time, with OpenTelemetry emerging as an essential component of modern observability. Our first objective for the research was to assess the awareness and perception of OpenTelemetry in the IT industry. We assumed the research would show that the project has some good momentum, but the results were even a bit higher than expected, with a majority (68.3%) of respondents saying they are moderately or very familiar with OTel.

OpenTelemetry also enjoys a positive perception, with half of respondents considering OpenTelemetry mature enough for implementation today, and another 31% considering it moderately mature and useful. So more than 80% basically feel that OpenTelemetry can be used now. And almost everyone surveyed (98.7%) expresses support for where OpenTelemetry is heading — a very strong vote of confidence. BTW those last two groupings include respondents that are only marginally familiar with OpenTelemetry, which suggests that OTel has a rock solid reputation.

The majority also say OpenTelemetry's role in observability is important — 61% believe OpenTelemetry is a very important or critical enabler of observability, and 57% place a similar value on the importance of OpenTelemetry to their own observability strategy.

The usage numbers are also encouraging. The report states, "Almost half (48.5%) of respondents currently use OpenTelemetry. Another 25.3% are not using OpenTelemetry yet, but are planning to implement. This means that just under 75% are either using or planning to use OpenTelemetry, a statistic that bodes well for the future of the standard. The remaining 24.8% are still evaluating, while only 1.5% of respondents had no plans to implement."

The survey findings further reflect the momentum of OpenTelemetry by showing how observability maturity correlates directly with the awareness, perception and even adoption of OpenTelemetry. A majority (64%) of survey respondents assess their own observability practices as mature or very mature, and 45% of that group are very familiar with OpenTelemetry; 67% see OpenTelemetry as very important or critical to their own observability strategy; and 61% already use OpenTelemetry.

Image
EMA

The EMA report holds much more interesting stats about OpenTelemetry that can be valuable to both observability practitioners and IT product vendors, answering questions such as:

  • Where are users deploying OpenTelemetry?
  • What are the concerns and challenges?
  • What are the benefits of OpenTelemetry?
  • What level of ROI are users gaining?
  • What are the expectations for OpenTelemetry's future?

One of the final points we made in the report: OpenTelemetry will become a competitive advantage for organizations across most industries. "One of the most consequential points to consider: the survey findings suggest that your competitors have already started using OpenTelemetry to improve digital performance, availability, and the user experience. With this in mind, if you have not already adopted OpenTelemetry, the time to start is now."

Pete Goldin is Editor and Publisher of APMdigest

The Latest

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...

New EMA Report: OpenTelemetry's Emerging Role in IT Performance and Availability

Pete Goldin
APMdigest

OpenTelemetry is quickly becoming a foundational element of observability, according to a new report I wrote in partnership with Dan Twing, President and COO of Enterprise Management Associates (EMA), titled Taking Observability to the Next Level: OpenTelemetry's Emerging Role in IT Performance and Reliability. The report was sponsored by Elastic, an APMdigest sponsor, as well as Apica, Beta Systems, Dynatrace, Embrace and SolarWinds.

WEBINAR APRIL 15: Unlocking the Future of Observability: OpenTelemetry’s Role in IT Performance and Innovation

OpenTelemetry (OTel) is an open source CNCF project offering a framework and suite of tools including APIs and SDKs that facilitate the generation, collection, and exporting of telemetry data for observability platforms and related tools. OTel collects logs, metrics and traces, and is expanding data types to include profiling and many other possibilities.

This report comes at just the right time, with OpenTelemetry emerging as an essential component of modern observability. Our first objective for the research was to assess the awareness and perception of OpenTelemetry in the IT industry. We assumed the research would show that the project has some good momentum, but the results were even a bit higher than expected, with a majority (68.3%) of respondents saying they are moderately or very familiar with OTel.

OpenTelemetry also enjoys a positive perception, with half of respondents considering OpenTelemetry mature enough for implementation today, and another 31% considering it moderately mature and useful. So more than 80% basically feel that OpenTelemetry can be used now. And almost everyone surveyed (98.7%) expresses support for where OpenTelemetry is heading — a very strong vote of confidence. BTW those last two groupings include respondents that are only marginally familiar with OpenTelemetry, which suggests that OTel has a rock solid reputation.

The majority also say OpenTelemetry's role in observability is important — 61% believe OpenTelemetry is a very important or critical enabler of observability, and 57% place a similar value on the importance of OpenTelemetry to their own observability strategy.

The usage numbers are also encouraging. The report states, "Almost half (48.5%) of respondents currently use OpenTelemetry. Another 25.3% are not using OpenTelemetry yet, but are planning to implement. This means that just under 75% are either using or planning to use OpenTelemetry, a statistic that bodes well for the future of the standard. The remaining 24.8% are still evaluating, while only 1.5% of respondents had no plans to implement."

The survey findings further reflect the momentum of OpenTelemetry by showing how observability maturity correlates directly with the awareness, perception and even adoption of OpenTelemetry. A majority (64%) of survey respondents assess their own observability practices as mature or very mature, and 45% of that group are very familiar with OpenTelemetry; 67% see OpenTelemetry as very important or critical to their own observability strategy; and 61% already use OpenTelemetry.

Image
EMA

The EMA report holds much more interesting stats about OpenTelemetry that can be valuable to both observability practitioners and IT product vendors, answering questions such as:

  • Where are users deploying OpenTelemetry?
  • What are the concerns and challenges?
  • What are the benefits of OpenTelemetry?
  • What level of ROI are users gaining?
  • What are the expectations for OpenTelemetry's future?

One of the final points we made in the report: OpenTelemetry will become a competitive advantage for organizations across most industries. "One of the most consequential points to consider: the survey findings suggest that your competitors have already started using OpenTelemetry to improve digital performance, availability, and the user experience. With this in mind, if you have not already adopted OpenTelemetry, the time to start is now."

Pete Goldin is Editor and Publisher of APMdigest

The Latest

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...

Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...

This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...

There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...