Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

The irony: world-class platform engineering teams spend a majority of their time trying to govern high-cardinality use cases. Otherwise bills go through the roof! This is a major problem with Observability 1.0 tools. From Charity Majors in The Pragmatic Engineer Podcast

28,807 görüntüleme • 1 yıl önce •via X (Twitter)

5 Yorum

Gergely Orosz profil fotoğrafı
Gergely Orosz1 yıl önce

Full episode: YouTube: Apple: Spotify: Summary and transcript:

PDF GPT profil fotoğrafı
PDF GPT2 yıl önce

Everyone is getting ahead with AI. You should be too. Summarize documents, craft emails, and generate custom content instantly with this powerful tool. It's like having ChatGPT tailored for your job. Try it for free.

Mustafa Akın profil fotoğrafı
Mustafa Akın1 yıl önce

@mipsytipsy I hate when I need to always think about cardinality of my metrics/logs/events. I love what Honeycomb did with their own storage engine years ago and its also now Clickhouse based solutions are accessible as aopen-source alternative.

Fatih Yildiz profil fotoğrafı
Fatih Yildiz1 yıl önce

@mipsytipsy Exactly!!! That's why we have a metric inventory and log pattern feature to show where you can govern and optimize the waste. Check . We are on a big mission to wire it from end to end from edge to destination. @edge_delta

Siddharth Pareek profil fotoğrafı
Siddharth Pareek1 yıl önce

@mipsytipsy Observability 1.0 can be a budget sink if you’re not ready for high-cardinality data. Next-gen solutions must tackle this or we’re stuck in cost-governance limbo. How do you balance coverage vs. cost? #PlatformEngineering #Observability #DevOps

Benzer Videolar