On This Page

Home / Edge/ Administering· Notifications/ Notification Targets/Slack Notification Targets

Slack Notification Targets

You can send Notifications to a Slack channel, using Slack’s Incoming Webhooks.

You can also use a Webhook Destination to send specific event data to Slack for a team’s attention. For more information, see our Slack/Webhook integration topic.

First, in your Slack workspace, use a Slack app to enable incoming webhooks.

Then, in the New Target modal, click Slack to expose the following additional options on the modal’s (single) General Settings left tab:

General Settings
​

Target ID: Enter a unique ID used to identify the target. This will show in the Target ID column of the Targets tab. You can’t change it later, so make sure you like it.

Configuration
​

Webhook URL: Add the full URL of your Slack Incoming Webhook. For example: https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX.

Retries
​

Honor Retry-After header: When toggled to Yes and the retry-after header is present, Cribl Edge honors any retry-after header that specifies a delay, up to a maximum of 20 seconds. Cribl Edge always ignores retry-after headers that specify a delay longer than 20 seconds.

Cribl Edge will log a warning message with the delay value retrieved from the retry-after header (converted to ms).

When toggled to No (the default), Cribl Edge ignores all retry-after headers.

Settings for failed HTTP requests: Automatically retries after unsuccessful response status codes, such as 429 (Too Many Requests) or 503 (Service Unavailable). Clicking Add Setting reveals a table where you can add retry parameters for individual failed HTTP requests. These include:

  • HTTP status code: The individual status code for which the retry parameters apply.
  • Pre-backoff interval (ms): How long, in milliseconds, Cribl Edge should wait before initiating backoff. The maximum interval is 600,000 ms (10 minutes).
  • Backoff multiplier: Base for exponential backoff. A value of 2 (default) means Cribl Edge will retry after 2 seconds, then 4 seconds, then 8 seconds, and so forth.
  • Backoff limit (ms): The maximum backoff interval, in milliseconds, Cribl Edge should apply. Default (and minimum) is 10,000 ms (10 seconds); maximum is 180,000 ms (180 seconds).

Retry timed-out HTTP requests: When set to Yes, Cribl Edge to automatically retries HTTP requests that have timed out. Defaults to No. Enabling this option exposes the following settings:

  • Pre-backoff interval (ms): How long, in milliseconds, Cribl Edge should wait before initiating backoff. Maximum interval is 600,000 ms (10 minutes).
  • Backoff multiplier: Base for exponential backoff. A value of 2 (default) means Cribl Edge will retry after 2 seconds, then 4 seconds, then 8 seconds, and so forth.
  • Backoff limit (ms): The maximum backoff interval, in milliseconds, Cribl Edge should apply. Default (and minimum) is 10,000 ms (10 seconds); maximum is 180,000 ms (180 seconds).