Telemetry and LiveDashboard
summary
Phoenix 1.5 ships native Telemetry events (e.g. phoenix.router_dispatch_stop) and a generated metrics module that maps those events to counters/summaries so LiveDashboard can attach handlers and update charts in real time. The pipeline uses telemetry.attach/execute under the hood, stores listeners in ETS, and the dashboard’s LiveDashboard metrics_live process receives formatted metrics and re-renders UI. Telemetry.span emits start/stop/exception automatically; integrations with StatsD, Prometheus and Datadog enable alerting and lower mean time to resolution.
AI-written summary · about
chapters (20)
- 0:00Start
- 1:35Telemetry and Observability
- 4:04Observability Pipeline in Elixir
- 4:23Attaching the Event to a Handler
- 6:15Event Execution
- 10:05Telemetry Metrics Module
- 12:15Telemetry Metrics Library
- 15:22Live Dashboard as a Telemetry Reporter
- 16:41Attaching Events in Live Dashboard
- 17:14Live Dashboard Macro
- 22:34What Does Telemetry Expose in Our Elixir
- 22:44Phoenix Telemetry Events
- 23:07Phoenix Endpoint Render Errors Event
- 23:23Socket and Channel Interactions
- 23:46Phoenix Channel Events
- 24:38Live View Events
- 25:14Ecto Telemetry Events
- 26:31Tags and Tag Values
- 31:34Spanning
- 35:38Closing Words
related talks
36mTelemetry and LiveDashboard
39mTelemetry ...and metrics for all
27mTelemetry: By The Numbers
19mTelemetry is Not Having to Hope
37mBeyond Getting Started: Using OpenTelemetry to Its Full Potential
39mObservable Elixir
39mMonitoring Elixir With OpenTelemetry
13mTelemetry Over Events: Developer-Friendly Instrumentation at American Express Mobile