How to Migrate 4K People to an In-House Incident and Alert Management System in a Month
summary
Describes replacing Opsgenie (a SaaS incident-and-alert-management product) with an in-house incident and alert management system at Ozon within one month. Covers keeping existing integrations and required features intact while migrating 4,000 users to the new system.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 6:51Why migrate from SaaS
- 10:21Emergency team
- 13:56Feature prioritization
- 17:14User prep
- 19:01Technical architecture
- 20:08Key challenges
- 22:34Launch and monitoring
- 24:40Q&A project debt
- 26:06Q&A solutions
- 27:51Q&A team support
- 29:22Q&A client impact
- 31:36Q&A reliability
- 33:45Q&A Open Source plans
- 34:50Q&A data aggregation
- 36:15Q&A user adaptation
- 37:42Q&A deadline reasons
- 38:44Q&A post-processing
- 40:35Q&A wrap-up
related talks
48mDevOps Transformation: Introducing Incident Management and Maximizing Monitoring Value
27mKeynote - How DevOps paved the road to ..
30mKeeping Your DevOps Transformation from Crushing Your Ops Capacity
42mReplacing four monitoring systems in four years and surviving
23mIncident Response, Management & Alerts - where they fit in CloudOps?
23mMotivational Leadership Driving Change Through Empowered Eng
05mDevOps and incident management: A recipe for success
15mAI Assistance for On-Call Engineer