How We Try to Make a Lion Bulletproof...
summary
ING sets up SRE to fix repeated outages (2014 headlines) and raise 96.84% monthly availability toward regulator expectations. A small centralized SRE team (≈6–7 engineers, supporting ~1,700 devs) builds a self-service pipeline that provisions Prometheus + Alertmanager instances, AMIs, and dashboards, wires alerts to Mattermost and SMS, and avoids taking on-call for other teams. Current pain: centralized Graphite/ELK failings and an average major-incident alert lag of 69 minutes. Prometheus is nearly production ready after a year.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 2:15Identifying reliability gaps
- 7:34Agile transformation and team setup
- 13:16Core challenges for SRE
- 16:51Implementing the SRE roadmap
- 24:31Tooling and automation strategy
- 26:58Journey and cultural evolution
- 32:14Key takeaways and conclusions
related talks
25mHow do we help enterprise to adopt SRE and DevSecOps practices?
08mSRE and Healthcare Data Compliance
36mModernizing Incident Response with LLMs, RAG, and the MCP
39mWhen SRE and Security Teams Meet to Face a Crisis
33mSecurity and SRE: Natural Force Multipliers
20mImplementing SRE in a Regulated Environment
42mHow REI built a DevSecOps culture from the start
35mSRE for [cyber]security