Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Integrate with Alert Logic
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 Alert Logic Integration to forward Alert Logic alerts to Jira Service Management. Jira Service Management determines the right people to notify based on on-call schedules– notifies email, text messages (SMS), phone calls, iOS & Android push notifications, and escalates alerts until the alert is acknowledged or closed.
How does the integration work?
When an alert is created in Alert Logic, an alert is created in Jira Service Management.
Set up the integration
Alert Logic is an API-based integration. Setting it up involves the following steps:
Add an Alert Logic integration in Jira Service Management
Configure the integration in Alert Logic
Add an Alert Logic integration
If you're using the Free or Standard plan in Jira Service Management, you can only add this integration from your team’s operations page. To access the feature through Settings (gear icon) > Products (under JIRA SETTINGS) > OPERATIONS, you need to be on Premium or Enterprise plan.
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 an Alert Logic 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 “Alert Logic”.
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 webhook URL.
You will use this webhook URL while configuring the integration in Alert Logic 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 Alert Logic
To configure the integration of Alert Logic with Jira Service Management, complete the following steps:
In Alert Logic, go to Management > Notifications > Webhooks.
Select +Add New.
Enter a name and title for the webhook.
Paste the integration API URL copied previously into URL.
Select Save.
Navigate to Management > Notifications > Policies.
Either edit or create a new policy.
Paste the webhook URL previously copied from Jira Service Management into Alert Recipients.
Select Save.
Sample payload sent from Alert Logic
Create Alert payload (in JSON format)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
{
"aggregated_alerts_count": 0,
"additional_content": [],
"alert_definition_type_id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"customer_id": 111111,
"data": {
"message": "Alert Date : 2016-01-15 21:53:09 GMT\nCustomer Name : Your-customer-name\n\nAlert Type : log\nAlert Name : Log Correlation Alert Test - Your-customer-name\nMessage Type : Unix DHCP IP Assigned\n\nLogEvent link:\nhttps://invision.alertlogic.net/log_message.php?id= XXXXXXXXXXXXX",
"alert_rule_id": 1111,
"source": "correlation_alert_rules"
},
"description": "Your-customer-name LogEvent: Log Correlation Alert - Your-customer-name",
"id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"product": {
"name": "Log Manager"
},
"severity": "warning",
"state": "created",
"tags": ["example_tag", "example_tag2"],
"timestamp": 1452894789,
"type": "correlation",
"deleted": false,
"notifications": [
{
"id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"timestamp": 1452894789,
"alert_id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"status": "pending",
"updated": 1452894789,
"policy_id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"target_id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"target_cid": 111111,
"target_label": "testing",
"target_channel": "webhook",
"target_target": "http://your-web-hook-url/",
"target_contact_id": null
}
]
}
Jira Service Management parses the payload as follows:
JSON
1
2
3
4
5
6
7
8
9
10
11
{
"aggregatedAlertCount" : 0
"description" : "Alert Date : 2016-01-15 21:53:09 GMT\nCustomer Name : Your-customer-name\n\nAlert Type : log\nAlert Name : Log Correlation Alert Test - Your-customer-name\nMessage Type : Unix DHCP IP Assigned\n\nLogEvent link:\nhttps://invision.alertlogic.net/log_message.php?id= XXXXXXXXXXXXX"
"message" : "Your-customer-name LogEvent: Log Correlation Alert - Your-customer-name"
"productName" : "Log Manager"
"severity" : "warning"
"source" : "correlation_alert_rules"
"state" : "created"
"type" : "correlation"
"tags" : "example_tag", "example_tag2"
}
Was this helpful?