Customer Centric Monitoring
summary
Focuses on concrete checks: TLS certificates (example: Postmark has an invalid TLS for 9 hours incident), synthetic browser flows using Playwright browser tests every five minutes, page speed monitored via Lighthouse CI and CrUX, and real error tracking with Sentry or GlitchTip where adding the SDK is two lines of code to get release, affected-users and slow HTTP/db spans. Mentions ClickHouse ingesting millions of logs/sec and options for global uptime checks like uptime-kuma, blackbox_exporter or oneuptime.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker background
- 2:10Why customer centric monitoring
- 3:37Six pillars of monitoring
- 4:21Uptime and certificate monitoring
- 9:41Page speed and web vitals
- 13:59Synthetic browser tests
- 17:33Structured logs and events
- 21:05Error tracking with Sentry
- 25:18HTTP transactions and third-party APIs
- 27:25Where to start and tools summary
- 29:10Q&A session
related talks
52mHolistic Monitoring
19mUser-centered observability: load testing, real user monitoring & synthetics
16mMonitoring your platform from multiple locations
41mCustomer Centric Observability at Scale Leveraging AIOps & OpenTelemetry
32mCustomer Centric Observability: How Intuit Reduced Time To Detect Customer Impact From 30+ Minutes To Under 3 Minutes.
33m100% Visibility
08mMonitoring Errors and Slowdowns Across JS Applications
23mMastering Monitoring & Alerting: Key to Seamless Performance