Notification Integrations

Connect and manage the third-party channels DAM Alerting delivers notifications to — Slack, Webhook, Splunk, PagerDuty, Microsoft Teams, and ServiceNow. Configuring a connection is separate from rule configuration; see DAM Alerting’s Delivery Channels section for how a rule selects and uses a channel.

Note

Email is a per-rule delivery channel configured on the alert rule itself — it isn’t a Settings > Integrations connection, and there’s no Email card on this page.

In this section

• Slack — connect Slack as a delivery channel.
• Webhook — connect a custom webhook as a delivery channel.
• Splunk — connect Splunk as a delivery channel.
• PagerDuty — connect PagerDuty as a delivery channel.
• Microsoft Teams — connect Microsoft Teams as a delivery channel.
• ServiceNow — connect ServiceNow as a delivery channel.

Prerequisites

Managing notification integrations requires Administrator or Super Administrator access to your ALTR account.

The Integrations Grid

Notification integrations are configured and managed from Settings > Integrations. The page presents a grid of provider cards: Slack, Webhook, Splunk, PagerDuty, Microsoft Teams, and ServiceNow. Each card shows the total number of configured connections for that provider, displaying Not configured when there are none and a Connected badge when at least one connection exists.

Manage a Provider’s Connections

Selecting a provider card opens a list of that provider’s configured connections.

To manage a connection:

1. Select Settings > Integrations in the navigation menu.
2. Click a provider’s card.
3. Toggle a connection’s row between Active and Inactive to enable or disable it.
4. Click Test on a connection’s row to send a test delivery.
5. Click a connection’s row to open its edit drawer, or use the row’s delete action to remove it.

Deletion is blocked while a connection is in use by one or more alert rules.

The Edit Drawer

The edit drawer pre-populates non-secret fields; secret fields such as tokens and webhook URLs appear blank and must be re-entered to change them. Saving an edit uses partial-update semantics: only the fields you submit are written, and omitting a field leaves its stored value unchanged.

When a connection’s deliveries are failing, the edit drawer shows a Delivery is failing warning. The drawer also offers a Send Test action, disabled while there are unsaved edits, that fires against the saved connection configuration rather than your in-progress changes.

Reliability and Security

• Delivery suppression. After ten consecutive delivery failures attributable to your configuration, ALTR suppresses the affected integration and retries with exponential backoff, from five minutes up to 24 hours, re-testing once the backoff window elapses.
• Webhook protection. Custom webhook destinations are validated against internal and metadata-service address ranges, both when saved and again at send time, to block requests to internal infrastructure.
• Write-only secrets. Channel credentials — tokens, keys, webhook URLs — are stored encrypted and can be set but never read back over the API.