Bridging observability gaps: How modern enterprises stop losing millions

In today’s digital-first era, IT and business teams are waking up to alerts that critical services are down, dashboards look fine, but real users are frustrated. Hidden blind spots in legacy monitoring put companies at risk for costly outages, user dissatisfaction and serious revenue losses. In 2025 alone, one in eight enterprises loses over $10 million per month to these issues, while about half lose more than $1 million every month due to undetected disruptions.

Why traditional observability fails

Most observability tools were built to watch internal systems: monitoring MELT (metrics, events, logs, traces) on owned servers, containers and apps. But the modern enterprise runs not only on custom code, but also on SaaS platforms, APIs, external cloud providers and multi-region networks. The health of Internet components—DNS, SSL, routing and ISP reliability — now directly impacts the user experience.

Traditional Application Performance Monitoring (APM) tools struggle to capture and interpret issues that arise beyond your infrastructure. As a result, even as backend metrics report “green,” users experience outages, slowdowns and errors that go undiagnosed.

End-to-end visibility: APM plus IPM

To close these blind spots, leading organizations now couple APM with internet performance monitoring (IPM). While APM provides an inside-out view — tracking internal code, system health and traces—IPM offers the outside-in perspective. It actively tracks global Internet health, the performance of APIs, cloud services, regional ISP health and more. Together, they provide teams with real-time, end-to-end visibility from code to end user, regardless of where the disruption occurs.

 You know what? Notably, organizations such as SAP, IKEA and Akamai have leveraged this dual approach to achieve significant improvements, including faster incident detection, reduced downtime and better alignment of IT and business outcomes. Teams can now measure the actual impact of service outages on customer satisfaction and revenue, not just system uptime.

The role of OpenTelemetry for data unification

OpenTelemetry (OTel) has emerged as the glue binding APM and IPM ecosystems. As an open standard, OTel standardizes a set of traces, metrics and records across heterogeneous systems. Adopting OTel helps enterprises avoid vendor lock-in, standardize cross-platform monitoring and reduce device creep and complexity, according to CNCF.

For instance, a retail enterprise could deploy OTel SDKs in its mobile and web apps, feeding telemetry data simultaneously to both APM and IPM systems and providing centralized, actionable dashboards for both operations and business analysis.

Why centralize observability operations

With increased complexity and the growing cost of fragmented tools, many enterprises are forming centralized observability teams. These teams standardize tool selection, enforce best practices and ensure that observability is aligned with business priorities — not just tech KPIs. This consolidation reduces licensing and training expenses, prevents tool sprawl and improves collaboration and agility.

EMA research and Elastic surveys confirm that centralized teams are most likely to champion IPM adoption, acknowledging that external Internet paths are now as critical as internal code paths to user experience and business outcomes.

Real-world use cases: Preventing blind spots and business losses

1. Retail e-commerce: Outage on Black Friday

Scenario: A global retailer experiences slow-loading web pages for customers in Asia during Black Friday, even as internal dashboards show healthy traffic and low server latencies.

Resolution: With IPM, the team traces the problem to a regional ISP routing issue affecting CDN performance in Asia. Early detection allows rerouting and preemptive communication with customers, saving millions in potential lost transactions and preserving brand reputation.

2. Digital communication platforms: Slack

Scenario: Slack relies on observability to ensure reliable and timely message delivery across the globe. When intermittent message lags are reported, traditional logs offer no clues.

Resolution: Observability tools correlate real user monitoring with backend performance and external API health, enabling rapid diagnosis and resolution of issues, thereby keeping communication flowing and minimizing disruptions.

3. Financial services: Real-time transaction monitoring

Scenario: A bank’s transaction engine periodically fails to update account records after third-party payment API integrations are disrupted by regional Internet outages. Internal APM tools do not register any code exceptions.

Resolution: By integrating IPM, the bank detects anomalies in Internet traffic patterns affecting APIs, resolves issues promptly and compounds trust in financial operations.

4. Healthcare applications: Telemedicine reliability

Scenario: A telemedicine platform faces sporadic video connection drops for patients in certain rural areas. Internal systems operate normally, leaving staff without clear answers.

Resolution: Combining IPM with APM reveals that last-mile ISP instability and DNS resolution issues are to blame, not core services or app code. With this knowledge, the provider helps users switch to more reliable networks and invests in geo-distributed failovers for critical APIs.

5. Education systems: Data pipeline and grade record integrity

Scenario: An education provider’s grading system silently overwrites student records due to a malfunction in pipeline integrations, undetected for days.

Resolution: With data observability, the team is alerted to anomalies in data freshness and schema changes within minutes, thereby preserving data integrity and protecting student outcomes.

The payoff: Modern observability in action

Organizations embracing centralized observability tools that support OpenTelemetry, consistently achieve:

• Faster incident resolution: Problems are identified and addressed within minutes, not hours.
• Lower operational costs: Fewer redundant tools and improved efficiency lead to tangible savings.
• Superior user experience: Monitoring what truly matters to end users closes gaps before they turn into headlines.
• Greater alignment with business goals: Observability metrics directly support business KPIs, safeguarding revenue and reputation.

In 2025 and beyond, observability is about much more than uptime it is the foundation for business resilience, customer trust and IT value generation.

This article is published as part of the Foundry Expert Contributor Network.
Want to join?