On-Call Integrations
.
Everbridge
Use the Everbridge integration for paging and on-call schedule retrieval.
Beta integration
This integration is currently in beta release status.
Beta integrations are still being tested, but can be enabled by any customer. Core connectivity is stable, but the integration may receive updates based on user feedback.
Populate the following fields to set up the integration:
Field | Description |
|---|---|
Authentication Method | Choose how you'd like to authenticate with this integration. The following methods are available:
Note: OAuth client credentials only support Notifications and Contacts endpoints. On-call scheduling and group lookup requires basic authentication. |
Region (Optional) | Select the region of your Everbridge instance. |
Credentials | If you selected Basic Auth as your authentication method, enter the Username and Password of the Everbridge account that AI Incident Assistant should use for API interactions. If you selected OAuth 2.0 as your authentication method, enter your OAuth Client ID, Oauth Client Secret, and (Optional) Token URL Override. |
Everbridge Organization ID | Numeric Everbridge organization ID. |
Everbridge Paging Targets
You can set up paging targets in Managed Incident Channels escalation workflows. These paging targets will receive a notification during an incident.
To add a paging target, go to the Search Query box and type the name of a group. Matching groups will appear in the menu to the right. Select a group to add it to the configuration.
You can also click + Add Manual Target to manually add a target without searching for it.
After selecting the group, populate the following information in the Configured Targets section:
Group ID - the ID of the targeted group in Everbridge
Display Name - the display name that will appear in the managed incident channel.
Description - description of the Everbridge target.
Click Save Targets to add it to your configuration.
Grafana OnCall
Configure the Grafana OnCall integration for on-call management and paging.
Beta integration
This integration is currently in beta release status.
Beta integrations are still being tested, but can be enabled by any customer. Core connectivity is stable, but the integration may receive updates based on user feedback.
Populate the following fields to set up this integration:
Field | Description |
|---|---|
Authentication Method | Choose how you'd like to authenticate with this integration. The following methods are available:
|
OnCall API Endpoint URL | Enter the OnCall API Endpoint URL from your Grafana instance's OnCall settings. |
Credentials | Enter the credentials that allow the integration to authenticate. If you selected OnCall API Key, enter the OnCall API Key. If you selected Service Account Token, enter the Service Account Token and Grafana Stack URL. (i.e., |
Custom Headers | Add custom HTTP headers to include with all API requests. For each header, include the Header Name and Header Value. To add additional headers, click the + sign. |
Deployment Type | Select whether your Grafana OnCall integration is Cloud or On-Prem. Certain integrations have endpoints that work only with one deployment type. Selecting the correct option automatically applies the right guardrails to the AI Incident Assistant agents. Note: On-prem integrations can connect via the Relay Client, enabling secure communication with infrastructure behind your firewall. |
Grafana OnCall System/Schema Nuances | Add notes to help AI Incident Assistant understand your Grafana OnCall environment. We highly recommend configuring this field, as it allows you to enter organization-specific information that enables AI Incident Assistant to provide more accurate and consistent results. For example, enter explanations of custom fields and when or how they should be used to handle user queries. |
Jira Service Management
Use the AI Incident Assistant Jira Service Management (JSM) integration to retrieve on-call schedules, rotations, and contacts.
The following JSM operations permissions must be enabled to use the integration:
read:ops-config:jira-service-managementread:jira-userread:meoffline_access
To set up the integration, click Connect JSM. You'll be redirected to the Atlassian page where you will need to grant AI Incident Assistant access to your Atlassian account. Click Accept to enable the integration.
In the web app Jira Service Management integration page, select whether your JSM Deployment Type is Cloud or On-Prem.
Certain integrations have endpoints that work only with one deployment type. Selecting the correct option automatically applies the right guardrails to the AI Incident Assistant agents.
Relay client
On-prem integrations can connect via the Relay Client, enabling secure communication with infrastructure behind your firewall.
Jira Service Management Paging Targets
You can set up paging targets in Managed Incident Channels escalation workflows. These paging targets will receive a notification during an incident.
To add a paging target, go to the Search Query box and type the name of a team. Matching teams will appear in the menu to the right. Select a team to add it to the configuration.
You can also click + Add Manual Target to manually add a target without searching for it.
After selecting the team, populate the following information in the Configured Targets section:
Team ID - unique ID of the JSM team.
Display Name - the display name that will appear in the managed incident channel.
Description - description of the paging target.
MIR3
The MIR3 integration is used for on-call notifications and schedule management.
Beta integration
This integration is currently in beta release status.
Beta integrations are still being tested, but can be enabled by any customer. Core connectivity is stable, but the integration may receive updates based on user feedback.
To configure the MIR3 integration, populate the following fields:
Field | Description |
|---|---|
Authentication Method | Choose how you'd like to authenticate with this integration. The following methods are available:
|
Regional Endpoint | Select the region of your MIR3 environment to automatically populate the endpoint. Or, you can enter a custom URL in the text box. |
Credentials | If you selected Username & Password as your authentication method, enter the Username and Password of the MIR3 account that AI Incident Assistant should use for API interactions. If you selected API Key authentication, enter a MIR3 API Key. |
Deployment Type | Select whether your MIR3 integration is Cloud or On-Prem. Certain integrations have endpoints that work only with one deployment type. Selecting the correct option automatically applies the right guardrails to the AI Incident Assistant agents. Note: On-prem integrations can connect via the Relay Client, enabling secure communication with infrastructure behind your firewall. |
System/Schema Nuances | Add notes to help AI Incident Assistant understand your MIR3 environment. We highly recommend configuring this field, as it allows you to enter organization-specific information that enables AI Incident Assistant to provide more accurate and consistent results. For example, enter explanations of custom fields and when or how they should be used to handle user queries. |
MIR3 Paging Targets
You can set up paging targets in Managed Incident Channels escalation workflows. These paging targets will receive a notification during an incident.
To add a paging target, go to the Search Query box and type the name of a recipient schedule. Matching recipient schedules will appear in the menu to the right. Select a recipient schedule to add it to the configuration.
You can also click + Add Manual Target to manually add a target without searching for it.
After selecting the recipient schedule, populate the following information in the Configured Targets section:
Recipient Schedule ID - the recipient paging target's schedule ID in MIR3.
Display Name - the display name that will appear in the managed incident channel.
Description - description of the paging target.
OpsGenie
The AI Incident Assistant OpsGenie integration is used for alerting and on-call management.
To configure the OpsGenie integration, enter your OpsGenie API Key.
You can also optionally add Custom Headers. Custom HTTP headers can be included with all API requests. For each header, include the Header Name and Header Value. To add additional headers, click the + sign.
OpsGenie Paging Targets
You can set up paging targets in Managed Incident Channels escalation workflows. These paging targets will receive a notification during an incident.
To add a paging target, go to the Search Query box and type the name of a schedule. Matching schedules will appear in the menu to the right. Select a schedule to add it to the configuration.
You can also click + Add Manual Target to manually add a target without searching for it.
After selecting the schedule, populate the following information in the Configured Targets section:
Schedule ID - OpsGenie ID of the targeted schedule.
Display Name - the display name that will appear in the managed incident channel.
Description - description of the OpsGenie target.
PagerDuty
The AI Incident Assistant PagerDuty integration is used for incident response and alerting.
In PagerDuty, generate a user token API key with the following permissions granted:
schedules.readservices.readusers.readusers.contact_methods.readincidents.writeincidents.read
To configure the PagerDuty integration, enter your PagerDuty Email address and a user token API Key.
PagerDuty Paging Targets
You can set up paging targets in Managed Incident Channels escalation workflows. These paging targets will receive a notification during an incident.
To add a paging target, go to the Search Query box and type the name of a service. Matching services will appear in the menu to the right. Select a service to add it to the configuration.
You can also click + Add Manual Target to manually add a target without searching for it.
After selecting the service, populate the following information in the Configured Targets section:
Service ID - the ID of the targeted service in PagerDuty.
Display Name - the display name that will appear in the managed incident channel.
Description - description of the PagerDuty target.
Click Save Targets to add it to your configuration.