• Products
  • Get started
  • Documentation
  • Resources

Integrate with CloudWisdom

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.

CloudWisdom logo

What does the integration offer?

Jira Service Management has a specific API integration with CloudWisdom. CloudWisdom sends alert notification messages to Jira Service Management API with detailed information. Jira Service Management acts as a dispatcher for these alerts, 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 created in CloudWisdom, an alert is also created in Jira Service Management automatically through the integration.

  • When a CloudWisdom alert has images attached to it, those images are also attached to the Jira Service Management alert.

Set up the integration

CloudWisdom is an API-based integration. Setting it up involves the following steps:

  • Add a CloudWisdom integration in Jira Service Management

  • Configure the integration in CloudWisdom

Add a CloudWisdom 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 CloudWisdom integration in Jira Service Management, complete the following steps:

  1. Go to your team’s operations page.

  2. On the left navigation panel, select Integrations and then Add integration.

  3. Run a search and select “CloudWisdom”.

  4. On the next screen, enter a name for the integration.

  5. Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.

  6. Select Continue.
    The integration is saved at this point.

  7. Expand the Steps to configure the integration section and copy the API key.
    You will use this key while configuring the integration in CloudWisdom later.

  8. Select Turn on integration.
    The rules you create for the integration will work only if you turn on the integration.

Configure the integration in CloudWisdom

To configure the integration of CloudWisdom(Netuitive) with Jira Service Management, complete the following steps:

  1. In CloudWisdom, go to the Notifications page and open the Opsgenie tab.

  2. Select Add Opsgenie.

  3. Enter values for the following fields:

    • Name​: Names the Notification.

    • Enabled​: Indicates notification is active.

    • API Key​: Copied from Jira Service Management

    • API URL​: Copied from Jira Service Management(if your account is in the EU instance)

    • Description​: Notification description.

    • Teams​: Comma-separated list of Jira Service Management teams that should receive this notification.

    • Recipients​: Comma-separated list of Jira Service Management agents that should receive this notification.

    • Tags​: Any tags used to categorise your notifications.

  4. Select Save.

  5. Enable Jira Service Management notifications from your policy configuration.

  6. Navigate to ​Monitoring ​> ​Alerts​.

  7. Select ​+ New Policy​ (or edit an existing one). A modal appears.

  8. Set the policy’s ​scope ​and ​conditions​.

  9. Navigate to ​Notifications​ > ​Add Notification​.

  10. For Notification Type, select ​”OpsGenie”​.

  11. Complete the policy configuration.

  12. Save the changes​.

Sample payload sent from CloudWisdom


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 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 { "apiKey": "CUSTOMER_GENERATED_OPS_GENIE_API_KEY", "message": "CRITICAL, 'EC2 Utilization at 100%' fired for 'mon01-usw2a'", "alias": "d7be1059-ac53-4f36-8e4d-3678741ed131", "teams": [ "team01", "team02" ], "recipients": [ "recipient01", "recipient02", "test@netuitive.com" ], "description": "a user defined description", "tags": [ "tag01", "tag02", "tag03" ], "event": { "type": "EXTERNAL_INFO", "category": "CRITICAL", "elementFqn": "us-west-2:i-81d9718a", "elementName": "mon01-usw2a", "elementType": "EC2", "elementTags": { "tag02": "tag02Value", "tag01": "tag01Value" }, "elementLocation": "location", "timestamp": "2015-03-26T18:05:10Z", "policy": { "name": "EC2 Utilization at 100%", "scope": { "elementName": "", "elementTags": { "tag01": "value01", "tag02": "value02" } }, "conditions": [ { "analytic": "actual", "metric": "Utilization", "operator": ">", "level": 99 }, { "analytic" : "analytics", "metric" : "metric", "operator" : "op", "level" : 9000 } ] } }, "eventLink": "https://uat.netuitive.com#/metrics?timeRangeDuration=14400&endTime=2017-06-19T21:09:05.230Z&event_id=6d840ad7-8ccb-4408-9f58-3caa5a56c5cd", "policyLink": "https://uat.netuitive.com#/policies/970f2e8e-1813-49f7-97df-7db8c6e1636d", "externalEvent": { "source": "ing.custom.event.source", "title": "ing.custom.event.title", "tags": [ { "name": "ing-custom-event-tag", "value": "ing-custom-event-tag-value" } ], "data": { "level": "INFO", "message": "warning event on ing.custom.server" } }, "images": [{ "elementFqn": "rss-home", "metricFqn": "netuitive.linux.network.eth0.packets", "url": "https://s3.amazonaws.com/com-netuitive-uat-use1-images/6ca80d50-b141-4336-a88a-b4cc8fe18220/2017/06/19/21-09-04-image-e5f713c8-4a36-4168-adb2-f11c3919b485.png" }] } }



Still need help?

The Atlassian Community is here for you.