• Products
  • Get started
  • Documentation
  • Resources

Integrate with AppOptics

The feature described in this article is currently rolling out to some Jira Service Management Cloud customers. It may not yet be visible or available on your site.

AppOptics logo

AppOptics provides a simple Web API, as well as language bindings and integration with collection agents such as "statsd" and "collectd" to make it very easy to store metric data in AppOptics data store. AppOptics creates alerts in Jira Service Management when configured thresholds for metrics are exceeded.

What does the integration offer?

Jira Service Management has a webhook integration with AppOptics. Use the integration to send AppOptics incidents to Jira Service Management API, with detailed information. Jira Service Management acts as a dispatcher for AppOptics alerts, determines the right people to notify based on on-call schedules– notifies via AppOptics, text messages (SMS), phone calls and 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 AppOptics, an alert is also created in Jira Service Management automatically through the integration.

  • When an alert is closed in AppOptics, the alert in Jira Service Management is also closed.

Set up the integration

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

  • Add an AppOptics integration in Jira Service Management

  • Configure the integration in AppOptics

Add an AppOptics 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 AppOptics 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 “AppOptics”.

  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 AppOptics 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 AppOptics

To configure the integration of AppOptics with Jira Service Management, complete the following steps:

  1. In AppOptics, go to the Account Settings page.

  2. Go to the Services tab.

  3. Select “Jira Service Management” from Available Services.

  4. Select (+) next to Configured Services to add a new service destination or select an existing one to edit.

  5. Paste the API key previously copied from Jira Service Management into API key.

  6. Select "create service".
    You can also specify comma-separated tags and responders for the Jira Service Management alerts.

Read more about the AppOptions integration.

Sample payload

JSON

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 { "alert": { "id": 4892664, "name": "test alert", "runbook_url": "runbook.com", "version": 2, "description": "test alert" }, "trigger_time": 1424793470, "conditions": [ { "id": 611876, "type": "above", "threshold": 1, "duration": 60 }, { "id": 61187, "type": "average", "threshold": 2, "duration": 40 } ], "violations": { "test-source": [ { "metric": "cpu", "value": 43, "recorded_at": 1424793470, "condition_violated": 611876 }, { "metric": "metric1", "value": 51, "recorded_at": 1427793470, "condition_violated": 611876 } ], "source" :[ { "metric": "metric2", "value": 3, "recorded_at": 1624793470, "condition_violated": 611876 } ] }, "metric": { "name": "disk_read", "type": "gauge" }, "measurement": { "value": 50, "source": "test-source" }, "measurements": [ { "value": 50, "source": "test-source" } ] }

 

Additional Help