What’s Driving the Rising Cost of Observability? - podcast episode cover

What’s Driving the Rising Cost of Observability?

Jan 30, 202525 minEp. 1507
--:--
--:--
Download Metacast podcast app
Listen to this episode in Metacast mobile app
Don't just listen to podcasts. Learn from them with transcripts, summaries, and chapters for every episode. Skim, search, and bookmark insights. Learn more

Episode description

Observability is expensive because traditional tools weren’t designed for the complexity and scale of modern cloud-native systems, explains Christine Yen, CEO of Honeycomb.io. Logging tools, while flexible, were optimized for manual, human-scale data reading. This approach struggles with the massive scale of today’s software, making logging slow and resource-intensive. Monitoring tools, with their dashboards and metrics, prioritized speed over flexibility, which doesn’t align with the dynamic nature of containerized microservices. Similarly, traditional APM tools relied on “magical” setups tailored for consistent application environments like Rails, but they falter in modern polyglot infrastructures with diverse frameworks.

Additionally, observability costs are rising due to evolving demands from DevOps, platform engineering, and site reliability engineering (SRE). Practices like service-level objectives (SLOs) emphasize end-user experience, pushing teams to track meaningful metrics. However, outdated observability tools often hinder this, forcing teams to cut back on crucial data. Yen highlights the potential of AI and innovations like OpenTelemetry to address these challenges.

Learn more from The New Stack about the latest trends in observability:

Honeycomb.io’s Austin Parker: OpenTelemetry In-Depth

Observability in 2025: OpenTelemetry and AI to Fill In Gaps

Observability and AI: New Connections at KubeCon

Join our community of newsletter subscribers to stay on top of the news and at the top of your game

For the best experience, listen in Metacast app for iOS or Android