# Observability Alerting

> Observability alerting workflow for signal quality, routing policy, and actionable thresholds. Use when alert rules need design or tuning to detect incidents with clear ownership and noise control; do not use for business-feature implementation logic. Use when this capability is needed.

- Skill: `tomevault-io/observability-alerting` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/observability-alerting`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/observability-alerting/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/observability-alerting

---


# Observability Alerting

## Overview
Use this skill to design alerting that catches real incidents quickly without overwhelming responders.

## Scope Boundaries
- Use this skill when the task matches the trigger condition described in `description`.
- Do not use this skill when the primary task falls outside this skill's domain.

## Shared References
- Alert threshold actionability rules:
  - `references/alert-threshold-actionability-rules.md`

## Templates And Assets
- Alert catalog template:
  - `assets/alert-catalog-template.csv`
- Alert noise review checklist:
  - `assets/alert-noise-review-checklist.md`

## Inputs To Gather
- Critical user/system failure modes.
- Available telemetry signals and quality.
- On-call routing and escalation policy.
- Historical false-positive/false-negative patterns.

## Deliverables
- Alert catalog with severity, owner, and runbook linkage.
- Threshold and routing policy.
- Noise-control and tuning plan.

## Workflow
1. Build initial alert catalog in `assets/alert-catalog-template.csv`.
2. Set thresholds using `references/alert-threshold-actionability-rules.md`.
3. Define routing/escalation by severity.
4. Validate with `assets/alert-noise-review-checklist.md`.
5. Publish tuning backlog and ownership.

## Quality Standard
- Alerts are actionable and owned.
- Critical paths have coverage with bounded noise.
- Paging vs non-paging intent is explicit.

## Failure Conditions
- Stop when alerts are noisy, non-actionable, or ownerless.
- Stop when critical failure modes lack alert coverage.
- Escalate when alert quality risks SLO breach response.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/kentoshimizu) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-15 -->