Alert Management

The CLI provides CRUD operations for alert rules. Alerts notify your team through various channels when incident conditions are met.

Manual incident capture works with alerts. If your application calls captureException() or another incident-driving SDK method, the resulting incident can trigger new_incident alerts the same way as an unhandled exception.

Channels

Channel	Description	Config Required
`email`	Email notification to one recipient	`to`
`slack`	Slack channel message	`slack_destination_id` or `webhook_url`
`discord`	Discord webhook message	`webhook_url`
`webhook`	Generic alert webhook	`target_url`

Condition Types

Condition	Trigger
`new_incident`	A new incident is created.
`incident_regressed`	A previously resolved incident regressed.
`error_spike`	An unusual spike in incident occurrences is detected.
`severity_threshold`	An incident's severity meets or exceeds the configured minimum.
`regression_after_deploy`	A regression is correlated to a deployment.

List Alerts

debugbundle alert list --project-id proj_01HXYZ...

Output:

{
  "alerts": [
    {
      "alert_id": "alt_01HABC...",
      "project_id": "proj_01HXYZ...",
      "channel": "slack",
      "condition_type": "new_incident",
      "service_id": null,
      "severity_min": "high",
      "cooldown_seconds": 86400,
      "is_enabled": true,
      "config": {
        "slack_destination_id": "11111111-1111-4111-8111-111111111111"
      }
    }
  ]
}

Flag	Type	Default	Description
`--project-id`	`string`	—	Required. Project to list alerts for.
`--limit`	`number`	`20`	Maximum number of alerts to return.
`--auth-file`	`string`	`~/.debugbundle/auth.json`	Path to auth state file.
`--json`	`boolean`	`false`	Output as JSON.

Create Alert

Email Alert

debugbundle alert create \
  --project-id proj_01HXYZ... \
  --channel email \
  --condition new_incident \
  --severity-min high \
  --cooldown 86400 \
  --config-json '{"to": "oncall@mycompany.com"}'

Slack Alert

debugbundle alert create \
  --project-id proj_01HXYZ... \
  --channel slack \
  --condition error_spike \
  --config-json '{"slack_destination_id": "11111111-1111-4111-8111-111111111111"}'

Discord Alert

debugbundle alert create \
  --project-id proj_01HXYZ... \
  --channel discord \
  --condition severity_threshold \
  --severity-min critical \
  --config-json '{"webhook_url": "https://discord.com/api/webhooks/..."}'

Generic Webhook Alert

debugbundle alert create \
  --project-id proj_01HXYZ... \
  --channel webhook \
  --condition regression_after_deploy \
  --severity-min high \
  --config-json '{"target_url": "https://myapp.com/alerts"}'

Create Options

Flag	Type	Default	Description
`--project-id`	`string`	—	Required. Project to create the alert for.
`--channel`	`string`	—	Required. Alert channel: `email`, `slack`, `discord`, `webhook`.
`--condition`	`string`	—	Required. Condition type: `new_incident`, `incident_regressed`, `error_spike`, `severity_threshold`, `regression_after_deploy`.
`--service-id`	`string`	—	Scope alert to a specific service.
`--severity-min`	`string`	—	Minimum severity to trigger: `low`, `medium`, `high`, `critical`.
`--cooldown`	`number`	`0`	Notification cooldown in seconds. Use `0` to disable suppression; maximum is `604800` (7 days).
`--config-json`	`string`	—	Required. Channel-specific configuration as JSON string.
`--is-enabled`	`boolean`	`true`	Whether the alert is active.
`--auth-file`	`string`	`~/.debugbundle/auth.json`	Path to auth state file.
`--json`	`boolean`	`false`	Output as JSON.

--severity-min high does not match low-confidence opaque browser-native captures by default: opaque window_error infers low, and opaque resource_error infers medium.

Update Alert

debugbundle alert update alt_01HABC... \
  --project-id proj_01HXYZ... \
  --severity-min critical \
  --cooldown 0 \
  --is-enabled true

Partial update — only the specified fields are changed.

Flag	Type	Description
`--project-id`	`string`	Required. Project that owns the alert.
`--channel`	`string`	Update channel type.
`--condition`	`string`	Update condition type.
`--service-id`	`string`	Update service scope (use `null` to clear).
`--severity-min`	`string`	Update minimum severity (use `null` to clear).
`--cooldown`	`number`	Update notification cooldown in seconds. Use `0` to disable suppression.
`--config-json`	`string`	Update channel configuration (use `null` to clear).
`--is-enabled`	`boolean`	Enable or disable the alert.
`--auth-file`	`string`	Path to auth state file.
`--json`	`boolean`	Output as JSON.

Delete Alert

debugbundle alert delete alt_01HABC... --project-id proj_01HXYZ...

Permanently removes the alert rule. No further notifications are sent.

Channel Configuration Reference

Email

{
  "to": "oncall@mycompany.com"
}

Each email alert rule targets a single recipient. Create additional rules if more people should receive email notifications. Email deliveries are batched into 10-second per-project, per-recipient digests so sudden incident bursts send one summary email instead of one message per incident.

Notification Cooldowns

Alert rules can set a notification cooldown so repeated matches for the same notification key do not send immediately again. The CLI flag is --cooldown <seconds>, where 0 disables suppression and the maximum is 604800 seconds (7 days). Cooldowns suppress notifications only; they do not merge incidents or change incident grouping.

Slack

Preferred connected destination configuration:

{
  "slack_destination_id": "11111111-1111-4111-8111-111111111111"
}

Direct webhook configuration is still available for automation that intentionally manages its own Slack webhook:

{
  "webhook_url": "https://hooks.slack.com/services/T.../B.../xxx"
}

For the simplest setup, use debugbundle slack connect-url to complete Slack OAuth in a browser, then reference the returned destination ID in alert rules.

Slack Destinations

Connected Slack destinations let agents and developers reuse the same Slack channel without exposing webhook URLs in alert configuration.

debugbundle slack connect-url --project-id proj_01HXYZ...
debugbundle slack list --project-id proj_01HXYZ...
debugbundle slack test 11111111-1111-4111-8111-111111111111 --project-id proj_01HXYZ...
debugbundle slack delete 11111111-1111-4111-8111-111111111111 --project-id proj_01HXYZ...

slack connect-url prints a browser URL for Slack OAuth and channel selection. slack delete remains available after downgrade and only succeeds once no alert rule or weekly report still references the destination. slack list remains readable after a downgrade to Free so preserved destination setup is still visible while Slack delivery stays paused.

Discord

{
  "webhook_url": "https://discord.com/api/webhooks/..."
}

Webhook

{
  "target_url": "https://myapp.com/alerts"
}

Next Steps

Webhook Management — Manage webhook subscriptions
Alerts — Alert system concepts and architecture
Cloud Workflow — Full cloud workflow overview
API Alerts — Alert API endpoints

Alert Management

On this page