Integrate with Wavefront
This article highlights a new alerting feature that's natively available in Jira Service Management which is gradually rolling out to some Jira Service Management Cloud customers. It may not yet be visible or available on your site.
What does the integration offer?
Use Jira Service Management's Wavefront Integration to forward Wavefront alerts to Jira Service Management. Jira Service Management acts as a dispatcher for these alerts and determines the right people to notify based on on-call schedules– notifies via email, text messages (SMS), phone calls, and iPhone & Android push notifications, and escalates alerts until the alert is acknowledged or closed.
How does the integration work?
When an alert is fired by Wavefront, an alert is created in Jira Service Management automatically through the integration.
When an alert is resolved in Wavefront, the alert will be closed in Jira Service Management automatically through the integration.
Set up the integration
Wavefront is an API-based integration. Setting it up involves the following steps:
Add a Wavefront integration in Jira Service Management
Configure the integration in Wavefront
Add a Wavefront integration
Bidirectional integrations aren’t supported in Free and Standard plans. All the other integrations are supported at a team level in Free and Standard; however, for their outgoing part to work, you need to upgrade to a higher plan. To add any integration at a site level through Settings (gear icon) > Products (under JIRA SETTINGS) > OPERATIONS, you need to be either on Premium or Enterprise.
Adding an integration from your team’s operations page makes your team the owner of the integration. This means Jira Service Management only assigns the alerts received through this integration to your team.
To add a Wavefront integration in Jira Service Management, 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 “Wavefront”.
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.
Select Continue.
The integration is saved at this point.Expand the Steps to configure the integration section and copy the API key.
You will use this key while configuring the integration in Wavefront later.Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.
Configure the integration in Wavefront
To configure the integration of Wavefront with Jira Service Management, complete the following steps:
In Wavefront, select Browse > Web Hooks.
Select Create.
Enter a value for Title.
Select "Alert Opened" and "Alert Resolved" for Triggers.
Paste the API URL copied previously into URL.
Select "application/json" for Content Type.
Enter a value for Web Hook POST Body Template or select Default Template.
Enter a value for Description.
Select Save.
Sample payload sent from Wavefront
JSON
{
"alertId": "1471312865666",
"notificationId": "ae63a700-9e0b-4c13-816b-5caa3acf4f63",
"reason": "ALERT_OPENED",
"name": "Example Alert",
"severity": "INFO",
"severitySmoke": false,
"severityInfo": true,
"severityWarn": false,
"severitySevere": false,
"condition": "mmax(5m, ts(~sample.requests.latency, env=production)) > 100",
"url": "https://try.wavefront.com/u/pSNB7gHXPn",
"createdTime": "08/16/2016 02:01:05 +0000",
"startedTime": "08/16/2016 10:05:21 +0000",
"sinceTime": "08/16/2016 10:03:21 +0000",
"endedTime": "",
"snoozedUntilTime": "",
"subject": "[INFO] OPENED: Example Alert",
"hostsFailingMessage": "app-6 (~sample.requests.latency) [env=production][az=us-west-2]\napp-7 (~sample.requests.latency) [env=production][az=us-west-2]\napp-9 (~sample.requests.latency) [env=production][az=us-west-2]\napp-20 (~sample.requests.latency) [env=production][az=us-west-2]\napp-10 (~sample.requests.latency) [env=production][az=us-west-2]\napp-15 (~sample.requests.latency) [env=production][az=us-west-2]\napp-14 (~sample.requests.latency) [env=production][az=us-west-2]\napp-13 (~sample.requests.latency) [env=production][az=us-west-2]\napp-11 (~sample.requests.latency) [env=production][az=us-west-2]\napp-12 (~sample.requests.latency) [env=production][az=us-west-2]\napp-19 (~sample.requests.latency) [env=production][az=us-west-2]\napp-8 (~sample.requests.latency) [env=production][az=us-west-2]\napp-17 (~sample.requests.latency) [env=production][az=us-west-2]\napp-18 (~sample.requests.latency) [env=production][az=us-west-2]\napp-16 (~sample.requests.latency) [env=production][az=us-west-2]",
"errorMessage": "",
"additionalInformation": "",
"failingSources": [
"app-6",
"app-7",
"app-9",
"app-20",
"app-10",
"app-15",
"app-14",
"app-13",
"app-11",
"app-12",
"app-19",
"app-8",
"app-17",
"app-18",
"app-16"
],
"inMaintenanceSources": [],
"newlyFailingSources": [
"app-17",
"app-7",
"app-19",
"app-13",
"app-20",
"app-15",
"app-6",
"app-11",
"app-16",
"app-18",
"app-8",
"app-9",
"app-14",
"app-12",
"app-10"
],
"recoveredSources": [],
"failingSeries": [
[
"app-6",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-7",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-9",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-20",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-10",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-15",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-14",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-13",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-11",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-12",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-19",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-8",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-17",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-18",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-16",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
]
],
"inMaintenanceSeries": [],
"newlyFailingSeries": [
[
"app-17",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-7",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-19",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-13",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-20",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-15",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-6",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-11",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-16",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-18",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-8",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-9",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-14",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-12",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
],
[
"app-10",
"~sample.requests.latency",
[
"env=production",
"az=us-west-2"
]
]
],
"recoveredSeries": []
}Was this helpful?