What does the integration offer?
Jira Service Management Compass has native integration with New Relic workflows. Use the integration to send New Relic issues to Jira Service Management’s Compass’s API with detailed information. Jira Service Management Compass acts as a dispatcher for New Relic issues, determines the right people to notify based on on-call schedules, notifies via email, text messages (SMS), phone calls and iOS and Android push notifications, and escalates alerts until the alert is acknowledged or closed.
This document describes how to configure the integration and details of data that Jira Service Management Compass receives from New Relic.
How does the integration work?
When an alert is created in New Relic Workflows, an alert is also created in Jira Service Management Compass automatically through the integration.
When an alert is closed in New Relic Workflows, the related alert automatically closes in Jira Service Management Compass through the integration.
When an alert is acknowledged in New Relic Workflows, the related alert is also acknowledged in Jira Service Management Compass automatically through the integration.
...
Add a New Relic integration in Jira Service ManagementCompass
Configure the integration in New Relic
Add a New Relic integration
| Info |
|---|
Bidirectional integrations aren’t In this release, only incoming integrations are fully supported in Free and Standard plans. All the other integrations are supported the Standard plan, at a team level in Free and Standard; however, for their outgoing part to work, you need to . To use outgoing integrations or the outgoing part of bidirectional integrations, upgrade to a higher plan. To add any integration at a site level through You can add this integration only from your team’s operations page. Adding an integration from your team’s operations page makes your team the owner of the integration. This means Jira Service Management Compass only assigns the alerts received through this integration to your team. |
To add a New Relic integration in Jira Service ManagementCompass, complete the following steps:
...
| Code Block |
|---|
{
"tags": "tag1,tag2",
"teams": "team1,team2",
"recipients": "user1,user2",
"payload": {
"condition_id": 1,
"condition_name": "test condition",
"current_state": "open",
"details": "CPU > 50% for 5 minutes",
"event_type": "INCIDENT",
"incident_acknowledge_url": "http://localhost/incident/1/acknowledge",
"incident_api_url": "http://localhost/api/incident/1",
"incident_id": 1,
"incident_url": "http://localhost/incident/1",
"owner": "John Doe",
"policy_name": "test policy",
"policy_url": "http://localhost/policy/1",
"runbook_url": "http://localhost/runbook/url",
"severity": "CRITICAL",
"targets": [
{
"id": "12345",
"link": "http://localhost/target/12345",
"name": "Test Target",
"labels": [
"production",
"hostname"
],
"type": "Server",
"product" : "productName"
}
],
"timestamp": 123456789000
}
} |
Payload parsed by Jira Service Management Compass (in JSON format)
| Code Block |
|---|
[
"owner" : "John Doe",
"severity" : "CRITICAL",
"policy_url" : "http://localhost/policy/1",
"teams" : [
"team1", "team2"
],
"target_name" : "Test Target",
"target_type" : "Server",
"policy_name" : "test policy",
"incident_url" : "http://localhost/incident/1",
"incident_acknowledge_url" : "http://localhost/incident/1/acknowledge",
"tags" : [
"tag1", "tag2"
],
"event_type" : "INCIDENT",
"incident_id" : "1",
"target_link" : "http://localhost/target/12345",
"runbook_url" : "http://localhost/runbook/url",
"recipients" : [
"user1", "user2"
],
"target_labels" : [
"production", "hostname"
],
"details" : "CPU > 50% for 5 minutes",
"state" : "open",
"condition_name" : "test condition",
"target_product" : "productName",
"timestamp" : "123456789000"
] |
...