Observable Web Applications
summary
Argues that client-side observability is the most important view of a web system and shows how to instrument it with error tracking, performance metrics and analytics. Demonstrates concrete failures: Stripe checkout undefined when js.stripe.com fails and unexpected token "<" from HTML error pages breaking JSON.parse. Shows measurable impact: orders API median 300ms to >2s during a spike and funnel conversions dropping 25% → 12%. Recommends capturing enriched client errors and Web Vitals (CLS) and names TrackJS and Request Metrics as practical tooling.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:43ABILITY TO UNDERSTAND THE STATE AND BEHAVIOR OF A SYSTEM WITHOUT NEEDING TO TOP IT FROM RUNNING
- 11:49FULL-ICEBERG DEVELOPER
- 20:24AN EXAMPLE WEB APPLICATION
- 31:00MEASURING THE USER PERCEIVED TIMINGS OF NETWORK TX, USE FLOWS, AND FUNCTIONS
- 46:30WHEN THERE'S NO TRAFFIC
- 48:19DATA PRIVACY
- 49:07NETWORKS * GEOGRAPHY
- 49:50DEEP SERVICE TRACEABILITY
- 52:06REQUEST METRICS.
related talks
32mExpect the Unexpected: How to Deal with Errors in Large Web Applications
38mOff the Beaten Path: Moving Observability Focus from Your Service
40mObservability for All!
30mOff the Beaten Path: Moving Observability Focus from Your Service to Your Customer
32mObservability for Frontend Engineers
22mFrontend Observability Odyssey
19mUser-centered observability: load testing, real user monitoring & synthetics
30m"Observability for the Front End"