惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
人人都是产品经理
人人都是产品经理
Cisco Talos Blog
Cisco Talos Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
V2EX
博客园 - 三生石上(FineUI控件)
Martin Fowler
Martin Fowler
WordPress大学
WordPress大学
D
Docker
S
SegmentFault 最新的问题
博客园 - 聂微东
美团技术团队
Apple Machine Learning Research
Apple Machine Learning Research
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Last Week in AI
Last Week in AI
M
MIT News - Artificial intelligence
F
Fortinet All Blogs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
GbyAI
GbyAI
L
LangChain Blog
Vercel News
Vercel News
博客园 - 叶小钗
MongoDB | Blog
MongoDB | Blog
Stack Overflow Blog
Stack Overflow Blog
H
Help Net Security
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
Engineering at Meta
Engineering at Meta
T
Threat Research - Cisco Blogs
T
Threatpost
Scott Helme
Scott Helme
T
Tailwind CSS Blog
Latest news
Latest news
Stack Overflow Blog
Stack Overflow Blog
Blog — PlanetScale
Blog — PlanetScale
The Register - Security
The Register - Security
罗磊的独立博客
P
Proofpoint News Feed
腾讯CDC
S
Schneier on Security
雷峰网
雷峰网
A
About on SuperTechFans
T
Tenable Blog
F
Full Disclosure
Cyberwarzone
Cyberwarzone
博客园_首页
有赞技术团队
有赞技术团队
K
Kaspersky official blog

Catchpoint Blog

SRE Report: AI optimism and the economics of effort SRE Report: Why fast is what users trust The SRE Report 2026: Defensible Ns SRE Report 2026: What surprised us, what didn't, and why the gaps matter most Why Synthetic Tracing Delivers Better Data, Not Just More Data A New Chapter: LogicMonitor + Catchpoint – A Personal Note from Mehdi Mezmo + Catchpoint deliver observability SREs can rely on The four pillars holding up your digital business, and what happens when they crumble When payments pause: lessons from a global payments outage Observability 2025 Decoded: What the DZone Report Means for SLO-Driven Ops The next evolution of WebPageTest has arrived, and it’s a game-changer The Monitoring Blind Spot That Could Cost You Black Friday Powering Mexico’s Digital Future: Expanded Internet Observability with Catchpoint The Next Chapter of WebPageTest: Your New Experience Starts Soon SRE Report Retrospectives — Have AIOps Predictions Held Up? When BGP becomes UX: The inside story of a SaaS routing decision gone wrong (or right) Session Replay explained: A guide to seeing digital experience through your user’s eyes Making the invisible visible: Are your cloud firewalls and DDoS protection really working? When metrics mislead: Inside the 2025 Retail Web Performance Benchmark The vendor trap: why your next outage won’t be your fault—but will be your problem LLMs don’t stand still: How to monitor and trust the models powering your AI Semantic Caching: What We Measured, Why It Matters The Annual SRE Survey Is Open—We Want to Hear from You Observability isn’t about the tool. It’s about the truth Invisible dependencies, visible impact: Lessons from the Google Cloud outage Real-time detection of BGP blackholing and prefix hijacks Leading analyst firm reveals the real cost of internet disruptions The Power of Over 3000 Intelligent Observability Agents Monitoring in the Age of Complexity: 5 Assumptions CIOs Need to Rethink Why Intelligent Traffic Steering is Critical for Performance and Cost Optimization Retail digital performance event recap: Key insights from IBM & Catchpoint Zendesk outage: A case for proactive monitoring and faster incident response Silence during chaos: Why the X outage is a call to arms for proactive monitoring The $1 Million Lesson: Building a Culture of Quality Through SLAs When AI tools fail: How to map your AI dependencies for proactive visibility Why Super Bowl 2025 was a triumph for Internet Resilience Why Internet Performance Monitoring is the new health check for IT organizations Why use Playwright in Catchpoint for synthetic monitoring Introducing WebPageTest Expert Plan: Real-Time Insights, Synthetic + RUM together in One Platform The shift to digital: How businesses are reshaping their priorities for 2025 The SRE Report 2025's Call to Action Monitoring in the Age of the Internet: DEM, IPM, and APM—What You Need to Know SSL Monitoring, Trust, and McLOVIN Performing for the holidays: Look beyond uptime for season sales success Lessons from Microsoft’s office 365 Outage: The Importance of third-party monitoring Web Performance Experts Look into the Future of Web Performance The hidden challenges of Internet Resilience: Key insights from 2024 report When SSL Issues aren’t just about SSL: A deep dive into the TIBCO Mashery outage The curious case of Marriott and the untold impact of web performance on revenue Preparing for the unexpected: Lessons from the AJIO and Jio Outage It’s time to stop neglecting the elephant in the room: Performance Matters! The Need for Speed: Highlights from IBM and Catchpoint’s Global DNS Performance Study Learnings from ServiceNow’s Proactive Response to a Network Breakdown Webinar Recap: Taking Web Performance to the Next Level Use the Catchpoint Terraform Provider in your CI/CD workflows Is the Internet ready for L4S? Takeaways from the CrowdStrike outage: third-parties can pose risk July 19th global IT outage reminds us of digital complexity Agentic AI: Powerful But Fragile—What You Need to Know Demystifying API Monitoring and Testing with IPM Cloudflare outage: another wake-up call for resilience planning Cloudflare’s Resolver Outage: More Than Just DNS Cloud Monitoring's Blind Spot: The User Perspective Connected Devices: Unlocking the next frontier of Internet Performance Monitoring Consolidation and Modernization in Enterprise Observability Catchpoint named a leader in the 2024 Gartner® Magic Quadrant™ for Digital Experience Monitoring Catchpoint Peak Performance Summit 2025: Redefining Observability for the Outcome Economy Catchpoint Expands Observability Network to Barcelona: A Growing Internet Hub Catch frustration before it costs you: New tools for a better user experience Creating the IPM Category: Catchpoint’s Journey to Leadership and the LogicMonitor Era AWS Outage: How do you prepare for the failure of your own safety net? Achieving stability with agility in your CI/CD pipeline APM vs Observability: Observing beyond APM APM vs Observability: What comes next? APM vs observability: why your definitions are broken AppAssure: Ensuring the resilience of your Tier-1 applications just became easier APM vs Observability: Both-and, not either-or 2024: A banner year for Internet Resilience 5 Actions you can take to improve digital performance Fast and furious: The importance of performance in the digital age How SAP achieved world-class uptime through modern observability How AI Turns Monitoring From “What Now?” Into “What’s Next?” How IPM helped a top tech brand catch an OpenAI outage before it became a crisis Google’s Agent-to-Agent (A2A) Protocol is here—Now Let’s Make it Observable Here’s the proof: What the fastest sites on the web have in common Going for gold: Testing the resilience of Olympic websites From SEO to AEO: Why Web Performance Is the Key to AI Search Success From the source to the edge: the six agent types you can’t ignore Getting Started with Traceroute How to Monitor AI Agents in Commerce Systems From refresh to results: the metrics that shaped Election Day 2024 coverage Escalating risk, shrinking margins: The 2025 Internet Resilience Report Don’t get caught in the dark: Lessons from a Lumen & AWS micro-outage ECN explained: Navigate congestion for faster, smoother data delivery DNS misconfiguration can happen to anyone - the question is how fast can you detect it? Diagnosing Wi-Fi failures that traditional tools miss: a case study Did Delta's slow web performance signal trouble before CrowdStrike? Customer Survey 2024: Unveiling insights and impact Critical Requirements for Modern API Monitoring
Why it’s time to move beyond APM: Monitoring from the user’s perspective
2025-09-09 · via Catchpoint Blog

For years, organizations have relied on Application Performance Monitoring (APM) as the backbone of their observability strategy. The idea was simple: collect as many logs, metrics, and traces as possible, then sift through the data to uncover insights.

But as applications have shifted to the cloud and become increasingly API-driven, that model has broken down. And according to Gartner’s April 2025 report Get Your Observability Spend Under Control, by Padraig Byrne, Martin Caren, and Matt Crossley, the financial impact of sticking with old approaches is now impossible to ignore.

The staggering reality of observability spend

The Gartner research paints a stark picture of runaway costs.  

A review of observability platform vendor proposals submitted to Gartner between 2023 and 2024 showed the following:  

  • The median Gartner client spend on observability platforms now exceeds $800,000 annually with a single vendor.  
  • The median spend increased by more than 20% with a single vendor.  
  • Four percent of clients spend more than $10 million with a single vendor.

Much of this exponential growth stems from the explosion in telemetry data, particularly logs, which are notoriously verbose and costly to store and analyze. The report states "Gartner clients spend significantly more on log analysis tools than other parts of observability. For larger entities, this can be more than half of total spend. However, few indicate that these solutions deliver half the value of observability.”

One client case study highlighted in the research shows the severity of this trend: their observability costs grew from less than $40,000 in 2009 to nearly $10 million by 2024—a compounding annual increase of approximately 40% over 15 years.

Traditional telemetry strategies miss the mark

Don't get me wrong—logs and traces have their place. They can be invaluable when diagnosing technical issues deep inside your systems.

But here's the fundamental problem: traditional telemetry doesn't tell you about your user's actual experience. As Gartner observes, "Clients often indiscriminately apply observability in their systems rather than targeting spending on the most important applications and services."

Your customers don't care about a spike in traces or whether debug mode was accidentally left on. What they care about is whether your service works when they need it. Can they log in? Can they make a purchase? Can they access the features they're paying for?

If the answer is "no," then it doesn't matter how sophisticated your telemetry pipeline is—you've already lost.

Why DEM and IPM are the way forward

This is why we believe organizations need to start shifting their investments toward Digital Experience Monitoring (DEM) and Internet Performance Monitoring (IPM).

  • DEM provides a direct view into the customer experience. With synthetic monitoring and real user monitoring, you can see exactly what your customers see—in real time. The Gartner research describes these technologies as providing "an efficient and fast time-to-value method for providing near-real-time feedback on service performance at a fraction of the cost of full observability."
  • IPM extends visibility into the critical infrastructure your applications depend on — CDNs, ISPs, third-party APIs, BGP routing, and the broader internet ecosystem. In today's interconnected world, application performance is only as strong as its weakest external dependency. When a critical API goes down or an ISP experiences routing issues, traditional APM tools provide little insight into these external factors affecting user experience.

Together, DEM and IPM shift the focus away from telemetry overload and toward what truly drives business outcomes: user experience, reliability, and trust. This approach aligns with modern application architecture, where the application stack no longer sits fully within your control or your own data center.

Implementing smarter spending through tiered observability

Gartner makes a critical point in their research: not every application deserves the same level of investment. Their recommended tiered approach provides a strategic framework for aligning spending with business value. Based on the Gartner application tiers and our interpretation of how observability stacks should align with the following tiers.

Note: Application characteristics and percentages are from Gartner's research. The "Observability Stack" column reflects our recommendations based on the tiered approach.

The way we see it, this tiered approach recognizes that observability costs can differ by almost an order of magnitude between tiers. By aligning spend with business value instead of treating every system as equally critical, organizations can improve overall visibility while controlling costs.

Gartner's study notes, "Gartner clients have indicated that they can reduce costs associated with telemetry ingest and storage by more than 30% by successfully implementing a telemetry pipeline."

The path forward: strategic action steps

The old model of observability—collect everything, analyze later—no longer makes financial or operational sense. Gartner's study projects: "By 2028, 80% of enterprises that do not implement observability cost controls will overspend by more than 50%."

To avoid this fate, we believe organizations should:

  1. Audit existing log collection and implement governance frameworks to eliminate unnecessary telemetry and reduce costs
  1. Deploy telemetry pipelines to filter, route, and transform data before expensive ingestion
  1. Categorize applications into business-value tiers and align observability investments accordingly
  1. Leverage vendor-specific cost controls that many organizations don't realize they already have access to
  1. Rationalize existing tool portfolios using frameworks like TIME and PAID models to eliminate redundancy

The bottom line

What matters most is the experience of your users. If you're not measuring and optimizing for that, you're investing in the wrong metrics.

It's time for organizations to evolve their mindset: from APM's endless telemetry collection to DEM and IPM's user-first perspective. Not only is this approach more cost-effective — it's the only way to ensure you're investing in the performance that truly matters: the performance your customers experience every single day.

Gartner states, "Organizations must be aware that this is not a one-time exercise. Staying in control of costs requires an ongoing change in behaviors, methodologies and technologies related to observability." Ultimately, companies that make this shift now will be better positioned to weather the continued growth in observability complexity while delivering measurable business outcomes.

For actionable next steps to optimize IT observability spend, check out our expert guide: A 7-Step Approach to Optimize Observability IT Expenditure.

Summary

For years, organizations have relied on Application Performance Monitoring (APM) as the backbone of their observability strategy. The idea was simple: collect as many logs, metrics, and traces as possible, then sift through the data to uncover insights.

But as applications have shifted to the cloud and become increasingly API-driven, that model has broken down. And according to Gartner’s April 2025 report Get Your Observability Spend Under Control, by Padraig Byrne, Martin Caren, and Matt Crossley, the financial impact of sticking with old approaches is now impossible to ignore.

The staggering reality of observability spend

The Gartner research paints a stark picture of runaway costs.  

A review of observability platform vendor proposals submitted to Gartner between 2023 and 2024 showed the following:  

  • The median Gartner client spend on observability platforms now exceeds $800,000 annually with a single vendor.  
  • The median spend increased by more than 20% with a single vendor.  
  • Four percent of clients spend more than $10 million with a single vendor.

Much of this exponential growth stems from the explosion in telemetry data, particularly logs, which are notoriously verbose and costly to store and analyze. The report states "Gartner clients spend significantly more on log analysis tools than other parts of observability. For larger entities, this can be more than half of total spend. However, few indicate that these solutions deliver half the value of observability.”

One client case study highlighted in the research shows the severity of this trend: their observability costs grew from less than $40,000 in 2009 to nearly $10 million by 2024—a compounding annual increase of approximately 40% over 15 years.

Traditional telemetry strategies miss the mark

Don't get me wrong—logs and traces have their place. They can be invaluable when diagnosing technical issues deep inside your systems.

But here's the fundamental problem: traditional telemetry doesn't tell you about your user's actual experience. As Gartner observes, "Clients often indiscriminately apply observability in their systems rather than targeting spending on the most important applications and services."

Your customers don't care about a spike in traces or whether debug mode was accidentally left on. What they care about is whether your service works when they need it. Can they log in? Can they make a purchase? Can they access the features they're paying for?

If the answer is "no," then it doesn't matter how sophisticated your telemetry pipeline is—you've already lost.

Why DEM and IPM are the way forward

This is why we believe organizations need to start shifting their investments toward Digital Experience Monitoring (DEM) and Internet Performance Monitoring (IPM).

  • DEM provides a direct view into the customer experience. With synthetic monitoring and real user monitoring, you can see exactly what your customers see—in real time. The Gartner research describes these technologies as providing "an efficient and fast time-to-value method for providing near-real-time feedback on service performance at a fraction of the cost of full observability."
  • IPM extends visibility into the critical infrastructure your applications depend on — CDNs, ISPs, third-party APIs, BGP routing, and the broader internet ecosystem. In today's interconnected world, application performance is only as strong as its weakest external dependency. When a critical API goes down or an ISP experiences routing issues, traditional APM tools provide little insight into these external factors affecting user experience.

Together, DEM and IPM shift the focus away from telemetry overload and toward what truly drives business outcomes: user experience, reliability, and trust. This approach aligns with modern application architecture, where the application stack no longer sits fully within your control or your own data center.

Implementing smarter spending through tiered observability

Gartner makes a critical point in their research: not every application deserves the same level of investment. Their recommended tiered approach provides a strategic framework for aligning spending with business value. Based on the Gartner application tiers and our interpretation of how observability stacks should align with the following tiers.

Note: Application characteristics and percentages are from Gartner's research. The "Observability Stack" column reflects our recommendations based on the tiered approach.

The way we see it, this tiered approach recognizes that observability costs can differ by almost an order of magnitude between tiers. By aligning spend with business value instead of treating every system as equally critical, organizations can improve overall visibility while controlling costs.

Gartner's study notes, "Gartner clients have indicated that they can reduce costs associated with telemetry ingest and storage by more than 30% by successfully implementing a telemetry pipeline."

The path forward: strategic action steps

The old model of observability—collect everything, analyze later—no longer makes financial or operational sense. Gartner's study projects: "By 2028, 80% of enterprises that do not implement observability cost controls will overspend by more than 50%."

To avoid this fate, we believe organizations should:

  1. Audit existing log collection and implement governance frameworks to eliminate unnecessary telemetry and reduce costs
  1. Deploy telemetry pipelines to filter, route, and transform data before expensive ingestion
  1. Categorize applications into business-value tiers and align observability investments accordingly
  1. Leverage vendor-specific cost controls that many organizations don't realize they already have access to
  1. Rationalize existing tool portfolios using frameworks like TIME and PAID models to eliminate redundancy

The bottom line

What matters most is the experience of your users. If you're not measuring and optimizing for that, you're investing in the wrong metrics.

It's time for organizations to evolve their mindset: from APM's endless telemetry collection to DEM and IPM's user-first perspective. Not only is this approach more cost-effective — it's the only way to ensure you're investing in the performance that truly matters: the performance your customers experience every single day.

Gartner states, "Organizations must be aware that this is not a one-time exercise. Staying in control of costs requires an ongoing change in behaviors, methodologies and technologies related to observability." Ultimately, companies that make this shift now will be better positioned to weather the continued growth in observability complexity while delivering measurable business outcomes.

For actionable next steps to optimize IT observability spend, check out our expert guide: A 7-Step Approach to Optimize Observability IT Expenditure.

This is some text inside of a div block.