Navigating the What, Where, and When of Your Frontend App
summary
A Confluence observability passport collects concrete checks: SLI/SLO/SLA (example SLA 99.9% with a 0.1% error budget), an SLO like 95% of requests under 200 ms, and owners plus response playbooks. It wires real tools—Sentry for errors and profiling, prom client for container metrics, defect dodger for vulnerabilities, and open telemetry plus jugger for distributed traces—so dashboards, alerts, logs, traces, profiles and product analytics show what broke, why CPU spikes from a dependent service affected frontend, and whether fixes actually work.
AI-written summary · about
chapters (9)
- 0:00Introduction and Speaker Background
- 0:17A Real-World Problem
- 1:45Understanding Observability
- 2:18Metrics and Their Types
- 4:16Service Level Agreements (SLAs)
- 5:53Error Budgets and Their Importance
- 8:24Setting Up an Observability Passport
- 12:06Advanced Observability Tools
- 15:25Conclusion and Final Thoughts
related talks
22mFrontend Observability Odyssey
32mObservability for Frontend Engineers
14mTracing: Frontend Issues With Backend Solutions
27mFrontend deserves monitoring too!
23mHow We Built a Complex SLO App Tightly Integrated with Grafana
29mObservability; a gentle introduction
26mObservability and Its Role in the Software Life Cycle
49mObservability in Practice: How to Become Proactive with Bugs