DORA Metrics Dashboard - Grafana Template
Pre-configured Grafana dashboard for tracking the four key DORA metrics: deployment frequency, lead time, MTTR, and change failure rate.
Comprehensive guides for building reliable systems and effective incident response processes.
81 articles, frameworks, and resources
Pre-configured Grafana dashboard for tracking the four key DORA metrics: deployment frequency, lead time, MTTR, and change failure rate.
Build a world-class incident management process. Learn frameworks for detection, response, communication, and learning from incidents to build more reliable systems.
Step-by-step incident response playbook for database outages with clear actions, diagnosis steps, and post-incident procedures.
Measure how quickly your team restores service after an incident. A key DORA metric that indicates your organization's resilience.
Track system availability and uptime percentage. Essential for SLAs, reliability, and customer trust.
Track the percentage of failed requests. Critical for reliability, user experience, and incident detection.
Track the percentage of deployments that result in failures, rollbacks, or hotfixes. Essential for balancing speed with stability.
A structured template for blameless incident analysis with timeline, root cause, and action items.
Map the evolution of observability tooling from custom scripts to SaaS platforms. Understand when to build, when to buy, and how to avoid the commodity trap.
A battle-tested framework for handling production incidents—from the first alert to the blameless post-mortem. Includes severity classification, escalation playbooks, communication templates, and lessons from real outages.
Joint advisory with international partners highlights malicious targeting of organisations from a range of sectors across the globe.
The week’s pattern: every “agent” rollout turned into a governance and energy conversation
AI adoption is forcing a pivot from “build smarter models” to “run safer systems”: faster vulnerability remediation, automated incident diagnosis, stricter identity/token controls, and explicit...
Engineering orgs are consolidating complexity into fewer, more controllable primitives (databases and constrained execution paths) while adding explicit governance mechanisms for AI outputs and...
AI is moving from experimentation to operational embedding (SRE, analytics, and autonomous agents), and the limiting factor is shifting from scale to trust: governance, security, auditability, and...
Engineering organizations are turning AI into an enforcement layer: standards, security, and reliability controls are being embedded directly into pipelines and runtime systems, rather than living as...
AI programs are shifting from single-model adoption to “AI operations” as a discipline: routing across multiple models, tightening safety controls, and rebuilding observability plus infrastructure...
AI agent adoption is shifting from demos to operational systems, forcing CTOs to treat agents as production software with SRE-grade telemetry, security controls, and cost-aware model routing.
Agentic AI is moving from stateless prompts to long-running workflows with persistent compute, tool execution, and enterprise governance.
RabbitMQ consulting: how to pick the right help and get real outcomes
Engineering orgs are adopting model-driven automation (graphs, state machines, continuous behavioral analysis) to keep reliability and security intact as AI-assisted and agentic development...
Engineering organizations are standardizing on agentic systems that execute multi-step work (incident investigation, code migrations, performance changes, data context building), which is forcing new...
Have experience to share? We welcome contributions from technical leaders.
Learn how to contribute