Developer Observability - the Forth Pillar
summary
Argues developer observability is a fourth pillar and demonstrates the ability to inject logs, metrics, snapshots into running production from an IDE (IntelliJ) without code changes, collapsing the CI/CD cycle of death and allowing live back-and-forth with users. Shows tagging of server agents for scale and integration with existing ingestion (Elastic). Describes security controls: sandbox and resource limits, admin audit logs, and block lists and PII reduction to prevent data leaks and abuse. Demo uses a LightRun-style agent.
AI-written summary · about
chapters (23)
- 0:00intro
- 0:21preface
- 0:38about shai
- 1:14shai's book
- 1:33logs, traces, metrics
- 4:11ci/cd cycle of death
- 4:34there are other problems over observing
- 7:27focused on devops
- 8:16microservices and serverless
- 8:54solution: developer observability
- 9:59works in ide
- 10:43inject: logs, metrics, snapshots
- 11:52injecting?
- 12:25security
- 13:52sandbox
- 14:28admin logs
- 14:53pii reduction
- 15:38block lists
- 16:17demo
- 19:34ephemeral
- 20:06insight
- 20:46summary
- 22:26thank you
related talks
16mUsing Observability to improve the Developer Experience
44mObservability: Superpowers for Developers
53mObservability Driven Development
29mObservability for Developers: How to Get From Here to There
33mWhat Developers Should Know About Observability
23mA peek into observability from a tester's lens
01h 10mObservability For (Java) Devs - 2023 Edition
31mObservability for Developers: How to Get There