Setting up Intelligent Observability
summary
Proposes a business architecture with three levels — dev/QA/prod, an events layer (logs, traces, network, security, UX) and a business/process layer tying customer, transaction and third‑party data — using OpenTelemetry and existing tooling. Emphasizes persona-based observability and automated self-healing so logs/traces/metrics correlate into end-to-end business visibility, surface process optimization opportunities, enable AIML/generative Ops to produce deep correlations, and map KPIs/SLAs to impacted processes for shared prioritization and automation planning.
AI-written summary · about
chapters (4)
- 0:00intro
- 0:21preface
- 0:39trends and shifts in intelligent observability
- 2:36a fresh business architecture approach needed
related talks
13mObservability Where are We Headed?
29mObservability; a gentle introduction
33mEffective observability in microservice architectures
48mAPI Observability by Design: Building Systems That Tell Their Own Stories
39mThe 5W’s of Observability with Practical Examples
27mOpening the Door to Observability
26mObservability and Its Role in the Software Life Cycle
33mWhat Developers Should Know About Observability