Final Bit: Automatic DevOps Management
summary
A small distributed team built an automated DevOps workflow that ingests errors and alerts from New Relic, Jenkins, browser JS clients and monitoring agents, turns them into tickets, deduplicates and classifies them with rule-based priorities, and applies rule-driven assignment. The workflow presents incidents, feature requests and support in a single Kanban board with WIP limits and pull-based work, measures average cycle time, and uses automatic bug ingestion to reduce context switching and improve service quality; the system was assembled in about two months and supports hundreds of customers.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:35Product development issues
- 5:52Hidden bugs
- 8:27Task overload chaos
- 10:37DevOps automation
- 13:57Kanban board tool
- 16:20Implementation results
- 17:51Limitations and future
- 19:41Q&A
- 27:18Conclusion
related talks
34mIncidents Happen
05mDevOps and incident management: A recipe for success
16mData Driven VSM for Quality Excellence
48mDevOps Transformation: Introducing Incident Management and Maximizing Monitoring Value
43mTo make mistakes is human. To auto-deploy it is DevOps.
30mHow DevOps is Enabling Lean Application Development
58mHow we killed DevOps by creating a dedicated DevOps team
45m200 Teams, 1 Goal: DevOps Maturity at Scale