Alert Rules

Alert rules define when Upmetr should create incidents and send notifications. You can set thresholds for infrastructure metrics, uptime monitors, SSL certificates, and cost budgets.

​

Creating an Alert Rule

1. Navigate to Alerts
2. Click Add Rule
3. Configure the rule settings
4. Click Save

​

Rule Settings

​

Trigger Types

​

Infrastructure Thresholds

For infrastructure agents, you can set metric-based thresholds:

​

Common Threshold Examples

​

Anti-Flapping

Alert rules use breach thresholds and recovery thresholds to prevent flapping:

​

Per-Agent Overrides

If a specific server needs different thresholds (e.g., a database server that normally runs at 80% memory), you can create per-agent overrides:

1. Open the alert rule
2. Click Add Override
3. Select the agent
4. Set the custom threshold
5. Click Save

The override applies only to that agent — all other agents use the default threshold.

​

Cooldown Period

The cooldown prevents notification spam:

• After an alert fires, the rule enters a cooldown period
• During cooldown, the same rule won’t fire again even if conditions persist
• Use shorter cooldowns (5-15 min) for critical alerts
• Use longer cooldowns (30-60 min) for informational alerts

​

Notification Routing

Alert rules work with notification rules to determine where alerts are sent:

1. Alert Rule triggers an incident
2. Notification Rule matches the trigger type and severity
3. Notification Channel delivers the message (Slack, email, SMS, etc.)

Configure notification rules at Settings > Integrations.

​

Enabling/Disabling Rules

Toggle any rule on or off from the alert rules list. Disabled rules stop evaluating — no incidents will be created.

​

CloudWatch Alert Thresholds

For AWS managed services monitored via CloudWatch, Upmetr includes 8 pre-configured critical rules: These are created automatically when you add a cloud account with CloudWatch access.

​

Troubleshooting