DZone’s 2025 Intelligent Observability Trend Report captures a real inflection point: teams are shifting from “more data” to outcome-driven practices that improve resilience and accountability.
The survey was gathered between August 28 and September 25, 2025, from a global pool of developers, architects, and IT professionals. The respondents represented seasoned practitioners (median ~15 years of experience) with diverse roles: 30% developers/engineers, 22% technical architects, and the remainder spanning SRE, DevOps, and IT leadership. This makes it a pragmatic snapshot of where observability is heading next.
The key finding: teams are moving away from collecting endless metrics toward measuring impact through Service Level Objectives (SLOs) and business outcomes. The next frontier is understanding not just what your systems emit, but what your users and customers actually experience. The idea of outcome-based observability is quite interesting to me, as I recently wrote an article on value-based observability that explored it in depth.
Here are the key findings from DZone’s report:
1. Open standards are now the default.
2. AI is real, especially for automation.
3. Compliance drives maturity.
4. End-user experience remains a blind spot.
5. Success metrics reflect a reliability-first culture.
Top metrics used:
6. Security observability lags behind.
Here’s our take on what these findings mean for ITOps and SRE leaders:
Pick OpenTelemetry as the contract for metrics, traces, and logs, and treat vendors as pluggable backends via the Collector. Lock down a common resource schema (service, env, region, customer) and a consistent sampling policy so correlation actually works. Then close the blind spots OTel can’t see by design: integrate active and passive Internet telemetry (DNS, BGP, TLS, CDN, last-mile network paths) to contextualise “good code, bad experience” moments.
In short: run OTel for app signals, feed synthetic/RUM and network path data alongside it, and correlate everything at the service and user-journey layers.
Start with a handful of golden journeys and write SLOs that reflect user-perceived latency, availability, and correctness. Route alerts through error budgets (burn rate alerts at multiple windows), not raw CPU or latency spikes.
Let SLOs drive data policy: keep high-res telemetry where it can change the budget, tier the rest. Tie spend to SLO risk. If a dependency burns budget, it gets engineering cycles or a contract review. This keeps ops work prioritized by impact, not noise. Consider embracing XLOs – eXperience level Objectives, which are more user-centric.
RUM tells you what real users just felt; synthetic tells you what the next user will feel. Both are critical for teams that value real-world user experience. Stand up synthetic tests for critical flows (login, search, checkout, auth to downstream APIs) from the geos and networks your customers actually use (synthetic tests from the cloud are not useful at measuring user experience), and include DNS, SSL/TLS, and CDN edge checks in the same runs.
Use RUM to tune thresholds, catch long-tail regressions, and bake these tests into change windows and release gates so you catch route leaks, cert drift, CDN config errors, and IdP hiccups before tickets flood in.
AI is great at triage and correlation when you feed it clean, comprehensive signals; it’s terrible at inventing packets you never measured. Start with narrow loops: event dedup, topology-aware correlation, suggested runbook steps, and root-cause analysis (RCA).
Dzone’s findings reinforce what we’ve been advising ITOps/SRE leaders: anchor reliability to SLOs, standardize on open telemetry pipelines, and pair RUM with synthetics to validate real-world journeys, not just dashboards. AI is already paying off in triage/automation, and compliance is now tied with observability strategy (DNS and BGP hijacks can be catastrophic).
Last but not least, the industry seems to be converging on the idea that more data is not better. Better data is better.
The DZone 2025 Intelligent Observability Report reveals a shift from data volume to outcome-based reliability. Teams are standardizing on OpenTelemetry, operationalizing SLOs, pairing RUM with synthetic testing, and using AI to drive smarter, faster incident response. The message is clear: More data isn’t better — better data is better.
DZone’s 2025 Intelligent Observability Trend Report captures a real inflection point: teams are shifting from “more data” to outcome-driven practices that improve resilience and accountability.
The survey was gathered between August 28 and September 25, 2025, from a global pool of developers, architects, and IT professionals. The respondents represented seasoned practitioners (median ~15 years of experience) with diverse roles: 30% developers/engineers, 22% technical architects, and the remainder spanning SRE, DevOps, and IT leadership. This makes it a pragmatic snapshot of where observability is heading next.
The key finding: teams are moving away from collecting endless metrics toward measuring impact through Service Level Objectives (SLOs) and business outcomes. The next frontier is understanding not just what your systems emit, but what your users and customers actually experience. The idea of outcome-based observability is quite interesting to me, as I recently wrote an article on value-based observability that explored it in depth.
Here are the key findings from DZone’s report:
1. Open standards are now the default.
2. AI is real, especially for automation.
3. Compliance drives maturity.
4. End-user experience remains a blind spot.
5. Success metrics reflect a reliability-first culture.
Top metrics used:
6. Security observability lags behind.
Here’s our take on what these findings mean for ITOps and SRE leaders:
Pick OpenTelemetry as the contract for metrics, traces, and logs, and treat vendors as pluggable backends via the Collector. Lock down a common resource schema (service, env, region, customer) and a consistent sampling policy so correlation actually works. Then close the blind spots OTel can’t see by design: integrate active and passive Internet telemetry (DNS, BGP, TLS, CDN, last-mile network paths) to contextualise “good code, bad experience” moments.
In short: run OTel for app signals, feed synthetic/RUM and network path data alongside it, and correlate everything at the service and user-journey layers.
Start with a handful of golden journeys and write SLOs that reflect user-perceived latency, availability, and correctness. Route alerts through error budgets (burn rate alerts at multiple windows), not raw CPU or latency spikes.
Let SLOs drive data policy: keep high-res telemetry where it can change the budget, tier the rest. Tie spend to SLO risk. If a dependency burns budget, it gets engineering cycles or a contract review. This keeps ops work prioritized by impact, not noise. Consider embracing XLOs – eXperience level Objectives, which are more user-centric.
RUM tells you what real users just felt; synthetic tells you what the next user will feel. Both are critical for teams that value real-world user experience. Stand up synthetic tests for critical flows (login, search, checkout, auth to downstream APIs) from the geos and networks your customers actually use (synthetic tests from the cloud are not useful at measuring user experience), and include DNS, SSL/TLS, and CDN edge checks in the same runs.
Use RUM to tune thresholds, catch long-tail regressions, and bake these tests into change windows and release gates so you catch route leaks, cert drift, CDN config errors, and IdP hiccups before tickets flood in.
AI is great at triage and correlation when you feed it clean, comprehensive signals; it’s terrible at inventing packets you never measured. Start with narrow loops: event dedup, topology-aware correlation, suggested runbook steps, and root-cause analysis (RCA).
Dzone’s findings reinforce what we’ve been advising ITOps/SRE leaders: anchor reliability to SLOs, standardize on open telemetry pipelines, and pair RUM with synthetics to validate real-world journeys, not just dashboards. AI is already paying off in triage/automation, and compliance is now tied with observability strategy (DNS and BGP hijacks can be catastrophic).
Last but not least, the industry seems to be converging on the idea that more data is not better. Better data is better.
This is some text inside of a div block.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。