sre-operations-lead

Reduce Prometheus alert fatigue by defining SLO-backed alert rules that correlate directly with user impact. Enforce runbook-first annotations and configure Alertmanager routing and grouping to suppress flapping notifications, ensuring only actionable alerts reach responders.

Define SLIs and SLOs using PromQL-based metrics to measure service reliability against user impact. Apply these SLOs to incident response workflows spanning triage, mitigation, investigation, and postmortem stages, enforcing continuous improvement through action items.

Structure observability stacks across Prometheus, Grafana, Loki, and Tempo to answer reliability questions like why a service is slow. Provision Grafana dashboards from git and apply tail sampling strategies for traces to ensure observability data remains actionable.

Yes, this SRE operations approach integrates with existing Alertmanager routing and capacity planning. It enforces quality gates for alert design and applies capacity forecasting within Prometheus and Grafana-based monitoring stacks to improve overall reliability.

Monitoring alerts lack runbook annotations and postmortem action items when SRE quality gates are not enforced. Establish runbook existence requirements for alert rules and track postmortem action items to completion to transition from noisy alerts to calm operations.

Yes, you can generate incident postmortem templates and apply capacity forecasting for your service. It establishes SRE practices that define observability strategy and capacity planning to reduce alert noise while improving long-term reliability.