Skip to main content

Open Source Is Dominating Observability

Open source dominance continues in observability, according to the Observability Survey from Grafana Labs.

A remarkable 75% of respondents are now using open source licensing for observability, with 70% reporting that their organizations use both Prometheus and OpenTelemetry in some capacity. Half of all organizations increased their investments in both technologies for the second year in a row.

The 2025 Observability Survey reveals that OpenTelemetry has continued its trajectory toward mainstream status with half of all organizations increasing their investments in the open source project for the second year in a row.

More than two-thirds of organizations (67%) use Prometheus in production in some capacity and while OpenTelemetry has less production usage (41%), it appears to have more momentum for future growth, with more than a third (38%) of respondents investigating it and only 6% reporting they have no plans to use OpenTelemetry at all. The survey also found that vendor neutrality and flexibility remain the most cited requirements for compatible observability solutions, directly aligning with OpenTelemetry's core value proposition.

"Our survey data confirms what we're seeing in the field — organizations aren't choosing between observability technologies, they're embracing multiple approaches to solve real-world problems," said Ted Young, developer programs director at Grafana Labs, cofounder of OpenTelemetry, and member of the OpenTelemetry Governance Committee. "This includes the growing adoption of both OpenTelemetry and Prometheus, two tools that work great together."

Other report findings include:

C-Suite Sees Importance of Observability

Roughly three-quarters of all companies say observability is business-critical at either the CTO, VP, or director level, with CTO being the most common response (33%). Organizations whose C-suite sees observability as business-critical are more likely to adopt more advanced tools and practices such as traces, profiles, SLOs, OpenTelemetry, and unified application and infrastructure observability.

Desire for AI to Tame Complexity Rises

The number one observability concern for respondents is complexity, while alert fatigue is cited as the biggest obstacle to faster incident response, so it's no wonder training-based alerts and faster root cause analysis topped respondents' AI/ML wishlist for observability.

Cost Management Remains Important, But Not Critical

Three-quarters of companies say cost is an important criteria when selecting observability technologies, though less than a third say they're concerned about observability costing too much — meaning organizations are more focused on getting value from their tools and techniques than just selecting the cheapest option.

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 ...

Open Source Is Dominating Observability

Open source dominance continues in observability, according to the Observability Survey from Grafana Labs.

A remarkable 75% of respondents are now using open source licensing for observability, with 70% reporting that their organizations use both Prometheus and OpenTelemetry in some capacity. Half of all organizations increased their investments in both technologies for the second year in a row.

The 2025 Observability Survey reveals that OpenTelemetry has continued its trajectory toward mainstream status with half of all organizations increasing their investments in the open source project for the second year in a row.

More than two-thirds of organizations (67%) use Prometheus in production in some capacity and while OpenTelemetry has less production usage (41%), it appears to have more momentum for future growth, with more than a third (38%) of respondents investigating it and only 6% reporting they have no plans to use OpenTelemetry at all. The survey also found that vendor neutrality and flexibility remain the most cited requirements for compatible observability solutions, directly aligning with OpenTelemetry's core value proposition.

"Our survey data confirms what we're seeing in the field — organizations aren't choosing between observability technologies, they're embracing multiple approaches to solve real-world problems," said Ted Young, developer programs director at Grafana Labs, cofounder of OpenTelemetry, and member of the OpenTelemetry Governance Committee. "This includes the growing adoption of both OpenTelemetry and Prometheus, two tools that work great together."

Other report findings include:

C-Suite Sees Importance of Observability

Roughly three-quarters of all companies say observability is business-critical at either the CTO, VP, or director level, with CTO being the most common response (33%). Organizations whose C-suite sees observability as business-critical are more likely to adopt more advanced tools and practices such as traces, profiles, SLOs, OpenTelemetry, and unified application and infrastructure observability.

Desire for AI to Tame Complexity Rises

The number one observability concern for respondents is complexity, while alert fatigue is cited as the biggest obstacle to faster incident response, so it's no wonder training-based alerts and faster root cause analysis topped respondents' AI/ML wishlist for observability.

Cost Management Remains Important, But Not Critical

Three-quarters of companies say cost is an important criteria when selecting observability technologies, though less than a third say they're concerned about observability costing too much — meaning organizations are more focused on getting value from their tools and techniques than just selecting the cheapest option.

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 ...