DevOps' Swiss Army knife for the BEAM
summary
Shows that calling io:format on a large message queue or tracing with redbug can blow node memory (a 10KB message repeated 5,000 times + pretty printing sends memory to ~5GB in seconds; redbug tracing fills memory in ~20s). Reviews etop, observer, recon and others, then describes extending WombatOAM with a feature‑driven distributed plugin architecture, a service catalog and request‑stream execution model that lets plugins accept, execute and clean up requests; demoed end‑to‑end integration and working safeguards.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:14Writing code
- 4:05Safety tools
- 5:20Observator
- 11:50Vimorium
- 15:00Problem analysis
- 19:07Execution framework
- 30:54Combat
- 31:39Demo
related talks
48mBEAM all the things
52mIs your JVM app flying blind? Unmask hidden issues with Observability superpowers!
51mHearts of Darkness: A Spring DevOps Apocalypse
11mPremiere
33mDevOps and the Rebirth of Childhood Innocence
44mThe Holy Trinity of Observability: Logs, Metrics, and Traces
39mWobserver: Easy to Integrate Monitoring and Debugging
34mChaos Debugging: Finding and Fixing Microservice Weak Points