On This Page

Home / Cribl Insights/ Alerts/ Notifications/Targets

Targets

Notification targets define where Cribl Insights sends alert notifications. Each target represents a delivery endpoint (for example, an email address, a Slack workspace/channel, a PagerDuty service, an AWS SNS topic, or a generic webhook URL). You create a target once and then reuse it across multiple Monitors, notification policies, and products.

Notification targets are shared across the Cribl Product Suite. This lets you keep routing consistent across your environment without recreating targets.

Target Types
​

Each target type exposes its own configuration fields. For example, URL and method for webhooks, routing key for PagerDuty, SMTP settings for email. Monitors and policies only need to know the target ID.

Create a Target
​

  1. In Cribl.Cloud, go to Insights > Alerts > Notification Settings.
  2. Select the Targets tab.
  3. Select Add Notification Target to open the New Notification Target pane.
  4. Enter a unique Target ID that clearly describes the channel or destination. For example, slack-prod-alerts or email-oncall.
  5. Choose a Target type.
  6. Complete the type-specific configuration fields.
  7. Save the target. It is now available to all notification policies and Monitors that reference targets.

Scope, Sharing, and Impact
​

  • A single target can be used by many Monitors and policies.
  • Editing a target (for example, changing a URL or routing key) affects all Monitors and policies that reference it.
  • Deleting a target breaks any configuration that points to it until you update those Monitors/policies to use a different target.

Treat targets as shared infrastructure objects:

  • Use clear, stable IDs (for example, slack-prod-alerts, pagerduty-platform-critical).
  • Avoid embedding environment-specific information into policies or Monitors when it belongs in targets. For example, use separate targets for different PagerDuty services rather than overloading one.

Considerations
​

Before you add or update targets:

  • Model channels by team and environment
    Create targets that mirror real ownership and escalation paths. For example, separate Slack or PagerDuty targets for platform versus app teams, or prod versus non-prod.

  • Reuse targets wherever possible
    Route different alert types through the same target using policies, rather than duplicating near-identical targets.

  • Control changes carefully
    Because a target is shared, coordinate edits with the teams that rely on it. If you need a different behavior for a subset of alerts, prefer creating a new target and updating only the relevant policies or Monitors.

  • Validate with test alerts
    After adding or editing a target, configure a temporary Monitor or policy to send a low-risk test notification and confirm delivery, format, and authentication.

Use notification targets to define where Cribl Insights sends alert notifications. Targets are reusable endpoints that can be referenced by notification policies and by monitors that use direct target assignment.