Setting Up Your First Alert
Create a destination and an alert rule in two minutes and start getting notified when something changes.
Monitoring without notifications is just logging. Let's make it reach you.
Alerts work in two steps: first you create a Destination (where the notification goes), then you create an Alert Rule that uses it.
Step 1: create a destination
Go to Dashboard > Destinations and click New Destination.
Name: something you'll recognize when picking it in a rule. "Team Discord" or "Manager Email" works fine.
Type: Discord, Slack, Email, or Webhook.
URL / Address: the webhook URL for Discord or Slack, the email address for email, or any HTTPS endpoint for a generic webhook.
Click Create Destination. It appears immediately in the list and is ready to use in rules.
Step 2: create an alert rule
Go to Dashboard > Alert Rules and click New Rule.
Name: something you'll recognize later. "Critical to Discord" works fine.
Destination: pick the destination you just created from the dropdown.
Minimum severity: the lowest level that triggers this rule. Pick Critical for track outages only, Info for everything.
Event types: leave empty to match all events at that severity, or pick specific ones.
Artist filter: leave empty for all artists, or limit to one.
Click Create Rule. Active immediately.
Three rules most teams start with
Critical outages to Discord
- Destination: Team Discord
- Min severity: Critical
- Event types: empty (all)
New releases to email
- Destination: Manager Email
- Min severity: Warning
- Event types: New Release Detected
Everything to a log channel
- Destination: Team Discord (or a separate #all-changes webhook)
- Min severity: Info
- Event types: empty (all)
Testing it
If changes were detected recently and your rule would have matched, you should already have a notification. Check the Changes feed to see if anything happened since you created the rule.
For Discord: make sure you copied the full webhook URL from Discord's Integrations settings. For email: check spam on first delivery.