7 things I’ve learnt while shadowing an SRE
Jun 25, 2020Olena Horal-Koretska

Summary
This post details learnings from shadowing an SRE, focusing on incident management, resource usage monitoring (Grafana, Kibana), resource allocation tradeoffs (CPU for PostgreSQL vs. Redis), SRE on-call veto power during incidents, interconnectedness of systems requiring debugging and log tracking, primary incident reporting sources (Prometheus alerting), and the SRE role in supporting and developing infrastructure beyond incident response. It highlights the importance of observability tools and understanding system behavior for effective incident management and infrastructure development.
More from the Log Management and Observability trail
- Green DevOps: Why carbon measurement belongs in your CI/CD pipeline
- Automate detection testing with GitLab CI/CD and Duo
- How to build CI/CD observability at scale
- Track vulnerability remediation with the updated GitLab Security Dashboard
- More granular product usage insights for GitLab Self-Managed and Dedicated