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

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

Enterprise IT environments have never been more observable ... Yet many organizations still grapple with outages, lengthy incident resolution cycles, and increasing complexity. Most teams do not suffer from a shortage of data. They struggle to determine what deserves attention and what action to take next ... Enterprise IT operations must move beyond monitoring and visibility. The next stage of maturity is decision operations, an approach that helps teams make faster, better-informed decisions ...

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

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

Enterprise IT environments have never been more observable ... Yet many organizations still grapple with outages, lengthy incident resolution cycles, and increasing complexity. Most teams do not suffer from a shortage of data. They struggle to determine what deserves attention and what action to take next ... Enterprise IT operations must move beyond monitoring and visibility. The next stage of maturity is decision operations, an approach that helps teams make faster, better-informed decisions ...