Ignite: Observability Observed
summary
Five minute lightning claim: observability is not just rebranded monitoring but a shift to measuring service health, asking arbitrary questions of systems, and finding emergent faults. Concrete tools and practices include the three pillars (metrics, logs, tracing), prefer structured logging for high‑cardinality one‑off failures, use distributed tracing or APM to follow requests, and deploy feature flags and canary deploys to test in production while correlating customer value or revenue back to specific systems.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:29What is Observability
- 0:59The LAMP Stack
- 1:14Microservice Mesh
- 1:29Cause and Effect
- 1:59Service Health
- 2:14Observability
- 2:44Three pillars of observability
- 2:59Metrics
- 3:29APM Distributed Tracing
- 3:44Dashboards
- 4:14Feature Flags
- 4:29Testing QA
- 4:44Revenue
- 4:59Outro
related talks
05mIgnite - Observability Observed
06mIgnite | Observability vs Monitoring - A Linguistic Analysis
29mObservability; a gentle introduction
33mWhat Developers Should Know About Observability
39mThe 5W’s of Observability with Practical Examples
35mObservability: Building Confidence & Answering the What, Where, How
32mThe Role of Observability in Cloud Native Environments
42mObservability can help you understand change