On-Call Knowledge Base
Searchable knowledge.
Overview
The on-call knowledge base captures operational knowledge in a searchable form. Tribal knowledge dies when the engineer who carries it leaves; the documented runbook library scales across the team and survives turnover.
- Searchable knowledge. Per-incident-type runbook; the on-call finds the right entry without paging the team.
- Per-service runbook. Per-service operational guide; matches ownership; the team that owns the service owns the runbook.
- Per-alert runbook. Per-alert response steps; supports response; the alert links directly to its runbook.
- PM-derived entries plus surface links. Per-PM the lesson captured; per-alert the runbook link in the alert payload.
The approach
The practical approach: per-alert runbook, PM-derived entries, linked from on-call surfaces, quarterly freshness review, documented per-team structure. The team’s discipline produces searchable operations instead of tribal knowledge.
- Per-alert runbook. Per-alert response steps; the on-call follows the runbook instead of investigating from scratch.
- PM-derived entries. Per-PM lesson captured as a runbook entry; the next similar incident has a runbook.
- Linked from surfaces. Per-alert runbook link in the alert payload; the on-call clicks one link, not two.
- Per-quarter review. Quarterly runbook freshness review; catches drift before it becomes incident-time discovery.
- Document the structure. Per-team KB structure committed to the handbook; supports onboarding.
Why this compounds
KB discipline compounds across runbooks and quarters. Each runbook produces ongoing on-call value; the team’s institutional knowledge grows; new joiners ramp on a current library.
- Better on-call response. Per-alert runbook; MTTR drops because the on-call follows known-good steps.
- Better onboarding. New on-callers benefit from accumulated runbooks; ramp is weeks faster.
- Better learning. PM-derived entries compound; the lesson library grows with each incident.
- Institutional knowledge. Each runbook teaches operational patterns; the team’s on-call muscle grows.
On-call KB discipline is an operational discipline that pays off across years. Nova AI Ops integrates with KB telemetry, surfaces patterns, and supports the team’s on-call discipline.