Configure Action Notifications

After creating an action, configure the action notifications using the Action Notification tab in the Configuration Editor.

Pulse supports multiple notification channels to send the execution details. Notifications are configured per cluster and can be enabled individually or in combination.

Notification Channels

Jira

Creates Jira issues automatically when actions are triggered.

Fields:

• enable: Turn Jira notifications on/off

• projectkey: Jira project key (e.g., OPS, DATA)

• username: Jira user/service account

• token: Jira API token

• url: Jira base URL (e.g., https://yourcompany.atlassian.net)

• issuetype: e.g., Incident, Bug, Task

• priority: e.g., P1, High (must match your Jira setup)

• labels: YAML list of labels

Slack

Sends real-time action notifications to Slack channels.

Options

• Enable or disable Slack notifications

• Send action notification to one or more Slack channels

• Use Incoming Webhooks for message delivery

Fields

• enable: Enables or disables Slack notifications

• defaultincomingwebhookurls: Slack Incoming Webhook URL(s)

Email

Delivers action notifications via email.

Options

• Enable or disable email action notifications

• Notify multiple recipients

• Use as a primary or secondary action notification channel

Fields

• enable: Enables or disables email notifications

• defaulttoemailids: Comma-separated list of recipient email addresses

Quantum

Creates outage or incident tickets in Quantum.

Options

• Enable or disable Quantum integration

• Automatically create outage tickets

• Control ticket type, state, and assignment

Fields

• enable: Enables or disables Quantum integration

• url: Quantum API endpoint

• subscriptionkey: Authentication key for Quantum

• tickettype: Type of ticket to create (for example, Reporting an Outage)

• state: Initial ticket state

• apporplatform: Application or platform name (Pulse)

• reportedby: User or system reporting the issue

• assignedto: User or group assigned to the ticket

xMatters

Triggers actions and escalations in xMatters.

Options

• Enable or disable xMatters notifications

• Notify on-call groups or escalation paths

• Integrate with xMatters APIs

Fields

• enable: Enables or disables xMatters integration

• url: xMatters REST API endpoint

• groupdetails: List of target groups or recipients

• alerttype: Notification category (default: ALERT)

• version: xMatters API version

BigPanda

Forwards action notifications to BigPanda for event correlation and noise reduction.

Options

• Enable or disable BigPanda integration

• Correlate related actions into incidents

• Reduce notification noise using snooze intervals

Fields

• enable: Enables or disables BigPanda integration

• maxbigpandamessagethreshold: Maximum number of messages per batch

• defaultsnoozeintervalinsecs: Default snooze duration in seconds

• url: BigPanda ingestion endpoint

• appkey: BigPanda application key

• authtoken: Authentication token

• mnemonic: Identifier used for action correlation

• overridealertonlyindicator: Controls notification-only forwarding behavior

Timezone Configuration

Controls how timestamps appear in action notifications.

Options

• Set timezone for actions

• Customize date and time format

Fields

• clienttimezone: Timezone used for action timestamps

• clientdatetimeformat: Date-time format for notifications

Apply the Changes

After updating and saving the Action Notification configuration, delete the ad-notifications and ad-axnserver pods so the changes take effect.