Monitoring environment stability with Erlang
summary
Erlang code that monitors QA environments runs periodic polls once a minute to once every five minutes, uses gen_server/gen_statem plus a rest_for_one supervisor layout to install generated child specs, and keeps a bounded history queue of state changes so disk usage stays small. It exposes a status API that returns atomic states and detailed data so CI can skip failing subsuites instead of reporting 87 false failures after 3–4 hour test runs. The system is built to detect instability not auto-restart resources and it works to reduce wasted CI runs.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:43Supervising Stability (cont.)
- 8:03Categories of Dependencies
- 18:20Architecting a monitoring application with erlang (cont.)
- 19:25Dependency Polling
related talks
41mIdioms for building fault-tolerant applications with Elixir
42mIt's about (run)time -- Elixir beyond the hype
01h 03mThinking Erlang in a connected world
44mIdioms for Building Fault-tolerant Applications with Elixir
53mIdioms for Building Distributed Fault-tolerant Applications with Elixir
45mTesting Asynchronous OTP
52mA Backpack to Go the Extra-Functional Mile
48mVM Tuning, Know Your Engine - Part III: The Scheduler