Your first stop for learning how to get started with Jira Service Management.
What does the integration offer?
users leverage to aggregate and manage alerts not only from but also from other sources. enables users to maintain their own notifications information and preferences, eliminates the burden of keeping this information current and accurate in multiple disparate tools.
This integration provides users with full alert lifecycle management capabilities. Use to not only receive notifications for critical problems detected by but also acknowledge alerts, take or assign ownership of the alerts, comment on them, etc. rapidly no matter when and where the alerts are received. keeps track of all alert activity seamlessly: when the alert is created, who is notified when and how, whether and when recipients see the alert, acknowledged it, who executes which action, etc. also automatically closes alerts when the host/service comes back up.
A short text message (SMS) is typically used to notify users often fails to convey sufficient information to enable the recipients to assess the problem and determine the right course of action. Jira Service Management alerts are not limited to couple hundred characters of text, and include many fields, tags, and capability for attached information. Recipients not only see the alert message, but all the supporting information, to figure out what to do next. Attach any information that is relevant to the alert and make it available to the recipients either via the API or the web UI.
How does the integration work?
When triggers an alert, an alert is created in automatically through the integration.
When the alert condition is no longer valid, makes another HTTP POST request to and closes the alert automatically.
When the alert is acknowledged/unacknowledged by , alert is acknowledged/unacknowledged automatically in as well (optional).
Set up the integration
is a bidirectional integration. Setting it up involves the following steps:
Add a integration in
Configure the integration in
Add a Circonus integration
To add a integration in , complete the following steps:
Go to your team’s operations page.
On the left navigation panel, select Integrations and then Add integration.
Run a search and select “”.
On the next screen, enter a name for the integration.
Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.
The integration is saved at this point.
Expand the Steps to configure the integration section and copy the webhook URL.
You will use this URL while configuring the integration in later.
Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.
Customize the integration
The integration uses sensible configuration defaults to make the integration as easy as possible. However, you can customize the integration:
Define different rules to notify different people for different alerts
Modify alert content using webhook payload
The following variables from alert webhook payload are available when defining filters and when setting the alert fields values:
Create multiple rules with filters using the variables from webhook payload. For each rule, alert fields are able to have different values, hence different people to be notified.
Acknowledge/Unacknowledge alerts in Circonus via Jira Service Management
The integration provides outgoing actions, too. If chosen, can acknowledge/unacknowledge alerts in . Select Send alert Updates Back to Circonus. Available actions are visible. Then choose the actions to send back to .
Configure a webhook in Circonus
To configure the integration of with , complete the following steps:
Go to **Menu next to logo.
Click Contact Groups.
Click NEW CONTACT GROUP +.
Enter a name for the contact group.
From Use Third Party drop-down menu, select Opsgenie.
Paste the API URL previously copied into Opsgenie API URL.
Copy the URL from Webhook URL and paste it into Circonus Webhook URL in the integration configuration page.
Create a ruleset that triggers an alert and add the new contact group to that.
Sample payload sent from Circonus to Jira Service Management
parses the payload as follows:
Sample payload sent from Jira Service Management to Circonus
Sample payload for Acknowledge action
Sample payload for Unacknowledge action