Skip to main content

Archetype: Alerting monitoring product

Use when​

Operations depend on catching anomalies, SLO breaches, or policy violations before customers do.

Common users​

  • SRE and platform teams
  • Fraud operations
  • Clinical safety monitors

Minimal MVP​

  • Signal ingestion with ack/escalation states
  • Alert rules with tunable thresholds
  • Runbook links per alert type
  • Noise metrics (MTTA/MTTR)

Required files​

  • product.yaml
  • product-brief.md
  • data-contract.md
  • evaluation.md
  • demo.md

Evaluation​

  • Precision vs alert fatigue
  • Time-to-detect critical incidents
  • False negative postmortems

Reference products​

  • Observability bridges with human runbooks

Common mistakes​

  • Firing unstructured pages with no remediation
  • Alert storms without suppression policies
  • Missing ownership metadata for paging

Agent prompt​

You are building an alerting microproduct. Enumerate severity classes, escalation trees, suppression windows, then wire the minimum pipeline that emits actionable notices tied to documented runbooks.