Browse documentation

Creating an alert profile

↩ Alerts & Notifications

An alert profile defines a condition to watch for and what to watch. This article covers creating one.

Set up at least one notification profile first — every alert profile needs one attached.

Creating a profile

In Settings, under Alerts, open Alert Profiles and create a new one.

Choose the type (this is fixed once saved):
- Up/Down monitoring — alert when something goes offline.
- Resource threshold — alert when CPU, memory, or disk crosses a limit.
- Log / trap event — match syslog patterns or SNMP traps.
Name the profile.
Attach notification profiles — tick one or more. These decide who's notified. At least one is required.
Set the general options:
- Max alerts and per period (min) — the rate limit.
- Send clear notification — also notify when the condition recovers.
Add assignments — what this profile watches: Global (all devices and servers), or a specific Site, Device, Server, Group, or Monitor.

Down threshold (min) — how long something must stay offline before the first alert (default 5).
Escalation tiers (optional) — add tiers, each with a delay (minutes). A tier re-notifies every attached notification profile after its delay if the alert is still active. Tier 1's delay counts from the initial alert; later tiers count from the previous tier.

Add one or more rules, each with:

A profile can have several rules (e.g. CPU > 90% and disk > 95%).

This type matches syslog lines or SNMP traps against patterns. It's aimed at more advanced setups and relies on the collector receiving those events.

The type can't be changed after a profile is created — create a new profile if you need a different type.
Start broad with a Global assignment, then add narrower profiles for systems that need tighter thresholds or faster escalation.