Don't wait to discover problems — let Sublyzer notify you when something goes wrong. Configure alerts to receive notifications via email or Discord when errors spike, performance degrades, or security issues are detected.

Email alerts are included with all plans. Configure them to receive notifications at your registered email address.

Setting up email alerts

1. Go to your integration settings
2. Navigate to the "Alerts" section
3. Enable "Email Notifications"
4. Configure which events trigger alerts
5. Set severity thresholds

Email alert options

Alert frequency

To prevent alert fatigue, configure how often you receive notifications:

• Immediate — Every qualifying event triggers an email
• Batched (15 min) — Grouped alerts every 15 minutes
• Batched (1 hour) — Grouped alerts every hour
• Daily digest only — Single email per day

PRO users can send alerts to Discord channels using webhooks or the Sublyzer Discord bot.

Option 1: Discord Webhook

1. In Discord, go to your channel settings → Integrations → Webhooks
2. Create a new webhook and copy the URL
3. In Sublyzer, go to Integration Settings → Alerts
4. Paste the webhook URL in the Discord section
5. Configure which events to send

Option 2: Sublyzer Discord Bot

1. Join the Sublyzer Discord
2. Invite the Sublyzer bot to your server
3. Link your integration with /sublyzer link [code]
4. Configure alerts with /sublyzer alerts

Discord message format

Create custom alert rules to get notified about specific conditions:

Rule components

• Metric — What to monitor (error rate, LCP, etc.)
• Condition — When to trigger (above, below, equals)
• Threshold — The value that triggers the alert
• Duration — How long the condition must persist
• Channels — Where to send the notification

Example rules

Rule: Error Rate Spike
  Metric: error_rate
  Condition: above
  Threshold: 5%
  Duration: 5 minutes
  Channels: Email, Discord

Rule: Performance Degradation
  Metric: lcp
  Condition: above
  Threshold: 4000ms
  Duration: 15 minutes
  Channels: Email

Rule: Security Alert
  Metric: vulnerability_count
  Condition: above
  Threshold: 0
  Duration: immediate
  Channels: Email, Discord

Alerts are categorized by severity to help you prioritize:

View all past alerts in the Alert History section:

• Timeline — Chronological list of all alerts
• Status — Triggered, acknowledged, resolved
• Details — Full context about what triggered the alert
• Actions — Acknowledge, snooze, or mark as resolved

Use alert history to identify patterns and tune your alert rules over time.

Too many alerts can be worse than too few. Follow these best practices:

For custom integrations, you can receive alerts via webhooks (PRO):

POST https://your-server.com/webhook
Content-Type: application/json
X-Sublyzer-Signature: sha256=...

{
  "event": "alert.triggered",
  "timestamp": "2024-01-15T10:30:00Z",
  "integration": {
    "id": "abc123",
    "name": "My Website"
  },
  "alert": {
    "id": "alert_xyz",
    "type": "error_spike",
    "severity": "high",
    "message": "Error rate increased to 5.2%",
    "metric": {
      "name": "error_rate",
      "value": 5.2,
      "threshold": 5
    }
  }
}

Learn more about webhooks: Webhooks Guide