Observability for Your Internal Developer Platform: Instrumenting Bac...
summary
Backstage backend gets Node.js auto-instrumentation with OpenTelemetry exporting traces and metrics to an OTel Collector and visualized in Grafana/Prometheus; Argo CD, GitHub Actions and SonarQube plugins (plus a create random number plugin) generate spans showing HTTP routes, trace IDs and 404/500 failures. Demo builds a pipeline with ngrok, Collector and alerting to Slack/PagerDuty, reproduces a missing plugin backend error, and proves that traces pinpoint the failing service, timings and resource attributes.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:07Backstage for infrastructure
- 4:17Backstage telemetry limits
- 6:21OpenTelemetry pillars
- 8:48Backstage + OpenTelemetry synergy
- 11:16Instrumenting Backstage
- 13:42Demo workflow setup
- 15:07Live demo config
- 17:38Backend instrumentation
- 18:19Scaffolder template
- 19:24Debugging with traces
- 21:53Error analysis in Grafana
- 24:23Alerts from OpenTelemetry
- 25:47Summary
- 26:08Q&A
related talks
23mImplementing Unified Observability: IDP on Backstage wit...
29mOTel You It's Not Just for Backend!
25mOpenTelemetry for Platform Engineers: Paving the Road To Self-Service Observability
23mOpenTelemetry Auto Instrumentation for Effortless Observability
53mUnmask hidden issues with Observability superpowers!
40mObservability for All!
32mObservability for Frontend Engineers
02h 02mHow To Troubleshoot and Monitor Applications using OpenTelemetry