Creating Alerts

Set up alerts to monitor your metrics and get notified when data changes unexpectedly.

Alert Types

Threshold Alerts

Trigger when a metric crosses a specified value. Supports operators: >, ≥, <, ≤, =, ≠, BETWEEN.

Revenue < $10,000

Anomaly Detection

Automatically detect unusual values using statistical analysis (Z-score). Configurable sensitivity: low, medium, high.

Orders per hour is anomalous

Trend Alerts

Detect significant changes in metric trends. Configure direction (up, down, either) and percent change threshold.

Revenue down > 20% week-over-week

Freshness Alerts

Monitor data freshness and alert when data becomes stale beyond a specified threshold.

Orders table not updated in 6 hours

Creating an Alert

Navigate to Alerts in your project
Click Create Alert
Select the alert type (threshold, anomaly, trend, freshness)
Choose a metric or data asset to monitor
Configure the condition and threshold
Set the evaluation schedule (how often to check)
Choose notification channels
Click Save

API Example

curl -X POST "https://api.lucaro.dev/v2/alerts" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Low Revenue Alert",
    "type": "threshold",
    "metric_id": "daily_revenue",
    "condition": {
      "operator": "<",
      "value": 10000
    },
    "schedule_cron": "0 */4 * * *",
    "severity": "critical",
    "notification_channels": ["email", "slack"],
    "recipients": ["analytics-team@company.com"]
  }'

Configuration Options

Option	Description
schedule_cron	Cron expression for evaluation frequency
severity	info, warning, or critical
mute_duration	Snooze period after firing (e.g., "1h", "24h")
cooldown_period	Minimum time between notifications
notification_channels	Array of channels: email, slack, webhook

Alert States

OK - Condition not met

Firing - Condition triggered

Muted - Temporarily silenced

Next Steps

Alert Conditions

Configure advanced conditions

Notification Channels

Set up email, Slack, webhooks