ObservaStack

Watchdog

# Watchdog

Larkspur Grocers is fictional. This note explains the alert. It is not an incident report. It does not record a page, a customer impact, or an MTTR.

## Signal

- Severity: `info`
- Team: `platform`
- Pending duration (`for`): none (intentional)

```promql
vector(1)
```

## What the condition means

vector(1) with no for duration. It is firing whenever rule evaluation works. The deadman receiver must see it. If it stops arriving, the alert pipeline is down. This is the only alert without a for duration.

## What an on-call would check

1. Read the expression above and the recording rules it uses.
2. Compare it with the promtool unit tests in `tests/rules/`. Every alert except Watchdog has a firing case and a non-firing case.
3. The annotation `runbook_url` is `https://runbooks.larkspur.example/Watchdog`. That host is a placeholder. This file is the copy in the repo.
4. This stack does not page anyone. Receivers use `*_file` credential paths and `example.invalid`.

返回告警目录