What this section is for
A rule compares a metric with a threshold and sends a notification to selected channels. Run Check evaluates rules manually. Scheduled checks require an administrator to enable ALERTS_AUTORUN_ENABLED in the server configuration.
When to use
- When a metric change needs a team response.
- After an incident, if a known metric could help identify a recurrence.
- When you want a notification if a metric passes an agreed threshold.
Quick start
- 1Configure notification endpoints first โ email, Slack, Telegram or webhook โ under Incident Notifications; a rule cannot deliver anything without one.
- 2Create a rule: pick the alert type, an operator, and a threshold.
- 3Select the endpoints it should notify.
- 4Use Run Check to evaluate rules immediately rather than waiting for the schedule.
Key settings
| Setting | What it does | How to use it | Common mistake |
|---|---|---|---|
| Alert type | Which condition the rule watches: bus factor, velocity drop, review bottleneck, knowledge gap or quality decline. | For each rule, agree who receives the message and what they will check. | Enabling many rules without deciding who will respond. |
| Operator and threshold | The comparison that decides when the rule fires. | Compare the threshold with recent team values so normal variation does not produce unnecessary messages. | Setting a threshold inside the normal range and receiving constant repeat alerts. |
| Delivery endpoints | Where the notification is sent. | Choose a channel read by the person responsible and test delivery. | Routing everything to a general channel where it competes with build notifications. |
Usage example
Scenario: A critical repository dropped to a bus factor of one and it was only noticed during a handover.
- 1Create a bus factor rule with a "less than" operator and a threshold of 2.
- 2Route it to the team channel, not to a personal inbox.
- 3Use Run Check to confirm it fires today, then enable server-side autorun if scheduled checks are required.
What this shows: You have tested a low bus factor alert and selected a channel the team reads. Regular checks require autorun to be enabled.
FAQ
Why can I not select an endpoint?
No active notification endpoints exist yet. Create one under Incident Notifications first โ the rule has nowhere to deliver to until then.
How often are rules evaluated?
Run Check evaluates them immediately. Background evaluation uses an hourly interval by default when ALERTS_AUTORUN_ENABLED is enabled; autorun is disabled by default.
Nothing fired, but the threshold was crossed. Why?
Check that the rule is enabled, that at least one endpoint is selected and active, and that the value was actually across the threshold at evaluation time rather than between two runs.
Tips
- Start with one rule and test both evaluation and delivery.
- Review thresholds and recipients periodically. If a message needs no action, refine or disable the rule.