NotebookLM for SRE: build a source-backed incident dossier
Use a curated notebook to compare runbooks and incident evidence, while keeping citations, freshness, and operational authority in view.
Search titles and article text.
Use a curated notebook to compare runbooks and incident evidence, while keeping citations, freshness, and operational authority in view.
Connect on-call interruptions, specialist demand, and recovery work to a concrete capacity decision using an on-call workload worksheet.
Turn reliability policy into a release decision with fresh evidence, limited exceptions, and a clear path to resuming normal changes.
A design guide for an incident assistant that handles duplicate events, partial failures, and reviewed AI summaries across tools.
A reusable prompt pattern for incident analysis, with checks for missing facts, unsafe recommendations, and unsupported certainty.
Measure a representative workload, identify the limiting resource, and test one reversible change instead of applying a universal sysctl recipe.
Locate the delay, choose a bounded intervention, and measure recovery quality alongside elapsed time.
Translate customer symptoms into an owned investigation while preserving impact, uncertainty, and a useful communication loop.
Decide which alerts earn an interruption using urgency, reachable authority, coverage evidence, and a practical alert acceptance record.
Use models for test suggestions and change analysis while keeping artifact identity, promotion rules, and rollback checks enforceable.
Examine what people knew and could do, then assign improvements that address the conditions behind the incident.
Download a Markdown runbook template and follow a database connection example that separates symptoms, mitigation decisions, and verified recovery.