Progressive Delivery with Observability
summary
Claims a concrete pipeline: a JavaScript Express app instrumented with OpenTelemetry and auto-instrumentation, deployed via CircleCI and observed in Honeycomb, with CI steps that query production telemetry and block promotion when beta error counts exceed zero. Built artifacts: app spans, build events, and a CI script that calls Honeycomb to count errors; observed example where beta shows 7 then 9 errors and the workflow fails, demonstrating a working data-driven progressive delivery gate.
AI-written summary · about
chapters (6)
- 0:00Progressive Delivery intro
- 0:43What is Observability
- 3:49Observability in deployment
- 8:21Testing in production
- 12:56Data-driven deployments
- 13:18Q&A
related talks
16mProgressive Delivery with Observability
22mProgressive Delivery: The Logical Evolution CI/CD
50mObservability and the Development Process
56mFast & Simple Deployments for Code & Infra
51mProgressive Delivery in the Kubernetes era
36mProgressive Delivery in the Kubernetes era
29mCombining Progressive Delivery with GitOps and Continuous Delivery
32mEvent-based Continuous Delivery: The End of the Monolithic Pipeline
