Site Reliability Engineering Standup

Template Overview

Site Reliability Engineers safeguard the operational foundation of production infrastructure. The SRE Daily Standup template structures daily operations around live system alerts, on-call incident handoffs, ongoing canary rollouts, and infrastructure automation tasks in plain Markdown.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "SRE Standup: [Squad Name] - [YYYY-MM-DD]"
date: [YYYY-MM-DD]
team: "[[SRE & Infrastructure Squad]]"
on_call_primary: "[[Primary Engineer Name]]"
on_call_secondary: "[[Secondary Engineer Name]]"
cluster_health: "Nominal / Degraded / Maintenance"
active_alerts_count: 0
tags: [sre, devops, standup, infrastructure, on-call, monitoring]
---

# SRE Daily Standup — [YYYY-MM-DD]

## 1. On-Call Incident Paging Review (Past 24 Hours)
| Alert Timestamp | Severity | Alert Trigger | Automated Action | Resolution Notes |
|---|---|---|---|---|
| 03:14 UTC | P3 (Low) | Disk usage >80% on backup node 4 | Log rotation executed | Disk cleared to 42%; nominal |
| 11:22 UTC | P2 (Medium) | Spike in ingress worker connection resets | Rerouted traffic | Upstream ISP fiber degradation |

## 2. Infrastructure Health & Cluster Status
- **Compute Cluster:** 99.98% availability; zero node kernel panics observed.
- **Edge CDN Gateways:** All regional endpoints responding within <12ms baseline latency.
- **Security Perimeter:** Zero abnormal port probes or unauthorized ingress detected.

## 3. Active Infrastructure Changes & Canaries
- **Canary Rollout:** Upgrading edge reverse proxies to Envoy v1.32; currently handling 10% traffic in European region.
- **Database Maintenance:** Vacuum and index re-index scheduled for staging environment at 22:00 UTC.

## 4. Daily Operational Commitments
- **[[Primary Engineer]]:** Complete post-incident review for yesterday's connection reset spike.
- **[[Secondary Engineer]]:** Migrate backup automation scripts to use local cryptographic keys.
- **[[Automation Lead]]:** Update Terraform templates for regional failover clusters.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "SRE Standup: Core Platform - 2026-10-09"
date: 2026-10-09
team: "[[Core Platform SRE]]"
on_call_primary: "[[Devin Zhao]]"
on_call_secondary: "[[Tarek Mansour]]"
cluster_health: "Nominal"
active_alerts_count: 0
tags: [sre, devops, standup, infrastructure]
---

# SRE Daily Standup — Core Platform — 2026-10-09

## 1. 24-Hour Review
Devin Zhao reported zero paging alerts over the past 24 hours. Primary compute nodes operated at 28% median CPU utilization.

## 2. Ongoing Projects
Tarek Mansour will deploy the updated socket-level egress blocking tests to the staging verification pipeline today, confirming that all worker containers remain strictly local.

When to Use and When to Avoid

When to Use

• Use daily for SRE, DevOps, and platform infrastructure engineering squads.
• Use to synchronize on-call paging incidents, cluster alerts, and planned maintenance.
• Use to maintain a historical log of infrastructure changes and canary progression.

When to Avoid

• Avoid using for consumer product feature design or UX discussions.
• Avoid using as a substitute for detailed post-mortem root cause analyses.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the SRE standup audio recording:
1. Extract all paging incidents, alert triggers, severity ratings, and resolution steps from the past 24 hours.
2. Summarize infrastructure cluster health metrics, edge latencies, and planned maintenance windows.
3. Itemize active canary deployments and individual operational commitments.
Output in clean, structured Markdown.

Your data remains securely on your Mac with zero cloud exposure.