Creating an alert rule
Go to Alerts and click Create Alert.Name the rule
Give it a descriptive name — e.g.
High error rate — support agent or Cost spike — prod.Choose a metric
| Metric | What it monitors |
|---|---|
error_rate | Fraction of operations that fail, timeout, or are rate-limited |
latency | Average response time in milliseconds |
cost | Total spend in USD for the window |
requests | Total operation count |
| Evaluator metric | Any custom eval score key (e.g. quality.score) |
Set condition and threshold
Choose an operator (
>, <, >=, <=) and the threshold value.Example: error_rate > 0.05 fires when more than 5% of operations fail.Set the evaluation window
The window controls how far back data is aggregated before comparing to your threshold.
| Window | Best for |
|---|---|
| 5 min | Sudden spikes — agent errors, cost bursts |
| 15 min | Sustained error rate increases |
| 30 min | Cost trend monitoring |
| 60 min | Latency degradation patterns |
Add notification channels
Add one or more channels. You can mix channel types on a single rule.Email — enter one or more addresses (comma-separated). Receives an HTML alert with metric, current value, threshold, and a direct link to the dashboard.Slack — paste your Slack incoming webhook URL. Alert arrives as a colour-coded message (red = critical, orange = warning, blue = info).PagerDuty — paste your Events API v2 integration key. Alert triggers an incident with severity mapped to the configured level.OpsGenie — paste your OpsGenie API key. Creates an alert with priority P1/P2/P3.Discord — paste your Discord webhook URL. Alert arrives as a colour-coded embed.Jira — enter your Jira base URL, email, API token, project key, and issue type. Creates a Jira issue when the rule fires.Freshservice — enter your Freshservice domain and API key. Opens a ticket with priority mapped to severity.Webhook — paste any HTTPS URL. Zespan POSTs a signed JSON payload. See Webhooks for the schema and signature verification.Use Test channel after adding a channel to verify delivery before the rule goes live.
Enabling and disabling rules
Each rule has a toggle on the rule card. Disabled rules are not evaluated and will not fire. Use this to pause a noisy rule without deleting it.Alert history
The history table shows every evaluation — both triggered and not triggered — with timestamp, rule name, metric value, and threshold. Click any row to see the full evaluation details.Webhook payload
When a rule fires and a webhook channel is configured, Zespan POSTs:X-Lumiqtrace-Signature-256 header for HMAC-SHA256 verification. See Webhooks for verification code.