Skip to main content
Push alert events from Nightingale (n9e) or Flashcat to Flashduty via webhook. When an alert is triggered, send a trigger event to Flashduty; when an alert recovers, send a recovery event to Flashduty. In the Nightingale/Flashcat v8.0.0-beta.7+ version, you can configure the collaboration space in the alert notification rules, no longer need to use routing rules.

​
Prerequisites

​
In Nightingale

  • You must have permission to modify System Settings=>Global Notifications or Alert Management=>Alert Rules.
  • Your Nightingale server must be able to access the domain api.flashcat.cloud to push alerts to the external network.

​
Supported Versions

This guide is compatible with Nightingale V5 and V6 versions.

​
Setup Steps

​
In Flashduty

You can obtain an integration push URL through either of these two methods:

​
Using Private Integration

Choose this method when you don’t need to route alert events to different channels - it’s simpler.

​
Using Shared Integration

Choose this method when you need to route alert events to different channels based on the alert Payload information.

​
In Nightingale/Flashcat

​
Configure in Nightingale/Flashcat v8.0.0-beta.7 +

In the new version, although you can configure the collaboration space directly in the alert notification rules, you still need to create a collaboration space in Flashduty and configure the dispatch strategy.

​
Step 1: Add Notification Media

  1. Log in to your n9e console, select Alerting > Media types and click Add
  2. Fill in the media name and identifier, select Flashduty type, and enter the integration push URL in the URL section
  3. Click Save and complete
drawing

​
Step 2: Configure Notification Rules

  1. Log in to your n9e console, select Alerting > Rules and click Add or edit the existing alert rules
  2. Configure the basic information as needed
  3. Select the Flashduty notification media added in the previous step
  4. Select the collaboration space (the collaboration space must be created in Flashduty in advance), and select other options as needed
  5. Click Save and complete
drawing

​
Step 3: Select Notification Rules in Alert Rules

  1. Log in to your n9e console, select Alerting > Alert Rules and click Add or edit the existing alert rules
  2. Select the Flashduty notification rule added in the previous step, and select other options as needed
  3. Click Save and complete
drawing

​
Configure in Nightingale/Flashcat v5~v8.0.0-beta.6

Choose one of the following two methods:

​
Method 1: Configure by Strategy

Select multiple alert rules and configure webhook in batch.
  1. Log in to your n9e console, select Alert Management > Alert Rules to enter the alert rules list page
  2. Select the alert rules you want to import in batch, choose batch update alert rules in the upper right corner
  3. In the popup, select the “Callback URL” field and enter the integration push URL in the new input box, as shown below:
drawing
  1. Return to the integration list, if the latest event time is displayed, the configuration is successful and events are being received
  2. Complete

​
Method 2: Global Configuration

Nightingale supports configuring global webhook URLs in both the interface and configuration file to push all alert events. Choose one of the following two methods.
V6 and Above
  1. Log in to your n9e console
  2. Go to System Settings-Notification Settings-Callback URL page
  3. As shown below, enable a new webhook, fill in the integration push URL in the URL section
drawing
  1. Complete
V5.4~5.15 Versions
  1. Log in to your n9e server instance
  2. Find and open the configuration file, usually etc/server.conf
  3. Modify the Alerting configuration section, add Webhook configuration as follows:
    config
    [Alerting.Webhook]
Enable = true
Url = "{api_host}/event/push/alert/n9e?integration_key=$integration_key"
BasicAuthUser = ""
BasicAuthPass = ""
Timeout = "5s"
Headers = ["Content-Type", "application/json", "X-From", "N9E"]
    Replace the Url parameter value with your integration push URL.
  4. Save the configuration file
  5. Restart n9e server to apply the configuration
  6. Return to the integration list, if the latest event time is displayed, the configuration is successful and events are being received
  7. Complete

​
Severity Mapping

Nightingale/Flashcat to Flashduty alert severity mapping:
n9eFlashdutyStatus
1CriticalCritical
2WarningWarning
3InfoInfo

​
FAQ