accelo config alerts notifications

Configuring Alert Notifications

The following command configures default alert notifications for Acceldata Pulse.

On entering the above command, the following inputs are required from you:

To find your Joda time zone value, see Joda Time.

ServiceNow Notifications

Line Notifications

Telegram Notifications

Jira Notifications

Opsgenie Notifications

To set up Opsgenie notifications, assign a value to following parameters after executing the config alerts notifications command.

Email Notifications

To set up email notifications, assign a value to the following parameters after executing the config alerts notifications command.

Quantum Notifications

To set up Quantum notifications, assign a value to the following parameters after executing the config alerts notifications command.

Sample Configuration

xMatters Notifications

To set up xMatters notifications, assign a value to the following parameters after executing the accelo config alerts notifications command.

Sample Configuration

xMatters Webhook Configuration (Pulse 4.1.2 or later)

Starting with Pulse 4.1.2, you can configure the xMatters notification channel to send alert notifications using a flexible, environment-driven approach.

Configuration Behavior

Introduced an environment variable:

• IS_XMATTERS_WEBHOOK

For details about behavior:

• If false → Use the generic webhook implementation (default for all clients)

• If true → Use the xMatters-specific request format

xMatters Payload Format

For details about payload behavior:

• When IS_XMATTERS_WEBHOOK = false (default):

The built-in generic request payload is used (For example):

• When IS_XMATTERS_WEBHOOK = true, use the following payload structure:

For details about payload:

• recipients → Comma-separated list of target users/groups

• summary → Short alert message

• description → Detailed alert context

• priority → Alert severity (e.g., LOW, MEDIUM, HIGH)

URL Configuration

For xMatters integration:

• If IS_XMATTERS_WEBHOOK = false (default) → The endpoint is automatically appended with /api/sendAlert

• If IS_XMATTERS_WEBHOOK = true→ The API endpoint is fully configurable and should be provided as required by xMatters

Summary

• Controlled via IS_XMATTERS_WEBHOOK

• Supports both generic and xMatters-specific formats

For client-specific configurations and validation, align accordingly.

Big Panda Notifications

To set up the Big Panda notifications, assign a value to the following parameters after executing the accelo config alerts notifications command.

In the configuration, the supported Mnemonic options are BDO and BDP.

This results in a request to BigPanda server:

• The source is always be "Pulse"

• Severity: Pulse severity to BigPanda severity mapping is as follows:

  • Critical => P2

  • High => P3

  • Everything else (low | medium | info) => P4

Microsoft Teams Notifications

To set up the Microsoft Teams notifications, assign a value to the following parameters after executing the accelo config alerts notifications command.

Create a Microsoft Teams Webhook URL

You can create the webhook URL using one of the following methods:

1. Using the Microsoft Teams application: See Create Incoming Webhooks for instructions.

2. Using Microsoft Workflows: See Create Incoming Webhooks with Workflows for detailed steps.

Important If using method 2 and your Microsoft Teams channel type is private, the target is set to “Chat with Flow bot” by default.

You must change it to a user who has permission to read messages in the private channel or authenticate the Flow bot to write to the private channel.

Netcool Notifications

To set up the Netcool notifications, assign a value to the following parameters after executing the accelo config alerts notifications command.

This results in a request to the Netcool server with the following fields:

• SEV (Severity): Valid values are CRIT or WARN. This determines the priority of the incident ticket. Pulse alert priorities map to Netcool severity as follows:

  • Critical → CRIT

  • High → CRIT

  • Low, Medium

  • Info → WARN

• COMPID (Component ID): Must be 3 to 64 characters and can contain only uppercase letters (A–Z), numbers (0–9), and underscores (_), with no spaces.

The Component ID identifies the affected application in ServiceFirst and indirectly determines the support queue where the ticket will be posted. The COMPID must already exist for the appropriate Application ITSI in ServiceFirst before generating alerts.

In Pulse, COMPID is tied to a specific cluster. Users configure this by running the accelo config alerts notifications command so that all alerts from that cluster send the configured COMPID.

• EID (Event ID): An integer between 0 and 99999 containing only digits. Pulse converts the Pulse Alert ID into this format when sending notifications.

• SOURCE (Source of the event): Must be 3 to 32 characters long and can include only uppercase letters, digits, underscores, and hyphens, with no spaces. This field always has the value: “PULSE_ALERTS_” + COMPID.

• SUMMARY (Summary): A freeform description of the problem, between 3 and 4000 characters. Only specific characters are allowed (letters, digits, spaces, and common symbols). Pulse incident details JSON is provided in this field.

• CI (Configuration Item / Node Name): Must be 3 to 64 characters and can contain only letters, digits, dots, underscores, and hyphens, with no spaces. This represents the node or server name related to the alert. Pulse uses the incident node hostname as the value.

• ERRTYPE (Error Type): Must be 3 to 64 characters and can contain only uppercase letters, digits, and underscores, with no spaces. Pulse uses the alert type as the value of this field when sending notifications.

• ALERTKEY (Alert Key): Must be 3 to 255 characters and can contain only uppercase letters, digits, dots, underscores, and hyphens, with no spaces. This is used to consolidate multiple alerts into a single incident ticket. If ALERTKEY is provided, Netcool deduplicates alerts using:

COMPID:SEV:ALERTKEY

If not provided, deduplication is based on: CI:SEV:COMPID:ERRTYPE:SOURCE:EID

Pulse derives this value from the Pulse Incident Reference ID after cleaning it to meet validation rules.

CLEAR (Clearing Indicator) Defines whether the alert is clearing. The only valid value is TRUE.

Options for [flags]

Enter the following command and append the below flags:

SEE ALSO

• accelo config alerts - Configures alerts for Acceldata Pulse