SupaGuardSupaGuard Docs
Guides

Configuring Alerts

Synthetic monitoring is useless if you don't know when things break. SupaGuard integrates with your existing tools to ensure the right person gets notified at the right time.

supported Integrations

We support direct integration with:

  • Slack: Get notified in a dedicated channel (e.g., #ops-alerts).
  • PagerDuty: Trigger incidents for on-call engineers.
  • Opsgenie: (Coming soon)
  • Intercom: (Coming soon)
  • Webhooks: Connect to any custom system or logic.

Setting Up an Alert Policy

An Alert Policy defines when and how you are notified.

  1. Go to Settings > Alert Policies.
  2. Click "New Policy".

Escalation Rules

You can define rules to avoid alert fatigue. For example:

  • Wait 2 minutes: If the site is down for less than 2 minutes, do nothing. (Filters out blips).
  • Notify Slack: If the issue persists, post to #alerts.
  • Wait 15 minutes: If still unresolved...
  • Notify PagerDuty: Wake up the on-call engineer.

Assigning Policies to Checks

Once created, you can assign a policy to any check:

  1. Edit your Check.
  2. Go to the Alerting tab.
  3. Select your policy from the dropdown.

Now, that check will follow the rules you defined, ensuring you are only bothered when it matters.

On this page