# Set up metric alerts that catch real problems without false alarms

Designs monitoring alerts for key business metrics with sensible thresholds, seasonality handling, and clear routing so people trust them.

- Topic: Data & Analysis
- Framework: Few-Shot
- Level: Advanced
- Tags: Data & Analytics, Fill-in Template
- Source: https://www.thinkwithprompt.com/prompts/set-up-metric-alerts-that-catch-real-problems-without-false-alarms

## Prompt

```text
Help me design alerts for key business metrics that catch real problems without crying wolf.

**Metrics to monitor:** [LIST with definitions, e.g. "hourly checkout conversion", "daily signups", "orders by payment method"]
**Historical data:** [PASTE recent history or describe typical level, daily and weekly patterns, and volatility]
**What a real problem looks like:** [e.g. "payment provider outage drops conversion to near zero"]
**Who responds and how fast:** [teams, hours, on-call or not]
**Tooling:** [e.g. BI tool alerts, dbt tests, SQL in a scheduler, Monte Carlo, custom Python]

Steps:
1. For each metric, recommend an alert method: static threshold, percentage change vs. same period last week, rolling mean with standard deviation bands, or a seasonal forecast with prediction intervals. Explain why.
2. Handle seasonality and calendar effects: time of day, day of week, holidays, campaigns, and month-end.
3. Set sensitivity: how many periods out of range before alerting, minimum volume so low-traffic hours do not trigger noise.
4. Separate data-pipeline alerts (late or missing data) from business alerts, so a broken pipeline is not mistaken for a business drop.
5. Define severity levels, routing, and what the alert message must contain (metric, expected vs. actual, link to dashboard, first checks to run).
6. Plan a tuning period: backtest the rules on history to estimate how often they would have fired.

Return:
- An alert design table: Metric | Method | Threshold logic | Minimum volume | Severity | Owner | Response time.
- Example alert message text.
- A backtest approach and code outline.
- A review cadence to retire or retune noisy alerts.
```

## What to fill in

- e.g. "payment provider outage drops conversion to near zero"
- teams, hours, on-call or not

Free to copy and use. From ThinkWithPrompt (https://www.thinkwithprompt.com/), a library of 2,663 curated AI prompts.