• Products
  • Get started
  • Documentation
  • Resources

Integrate with SOASTA

If you’re a customer who shifted your operations from Opsgenie to Jira Service Management, adding new instances of this integration isn’t possible in Jira Service Management. You can only edit the integrations that originally shifted from Opsgenie.


What does Jira Service Management offer SOASTA users?

Jira Service Management SOASTA integration enables SOASTA mPulse to create alerts in Jira Service Management when an alert is created in mPulse.

Functionality of the integration

  • When an alert is created on SOASTA, an alert is created on Jira Service Management automatically through the integration.

Edit SOASTA integration in Jira Service Management

To edit a SOASTA 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.

  3. Search for your SOASTA integration.

  4. Edit the integration settings and rules as necessary.

Configure the integration in SOASTA mPulse

Use the instructions in this section if applicable.

  1. In SOASTA mPulse, go to the "Alerts" page and click the New button (+).

  2. Fill out required fields in "The Basics, Choose a Data Event" and "Specify time options for when to monitor the event" sections.

  3. In "Choose an action type(s)" section, click Call Webhook.

  4. Select POST as the "Method" and paste the integration API URL into "URL" field.

  5. Type Content-Type: application/json into "Headers" field.

  6. Copy the content of "Sample Body Field" section in this documentation, and paste it into the "Body" field in SOASTA mPulse.

  7. Drag corresponding attributes from "Attributes" field and drop them in-between the corresponding quotes.

  8. Click Save.

SOASTA alert details

Sample payloads sent from SOASTA to Jira Service Management


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 { "alert_name": "Simple Alert", "severity": "MEDIUM", "app_name": "jsm", "beacon_count": "3", "bounce_rate": "9", "network_error_rate": "12", "page_load_time": "152 ms", "dns_resolution_time": "81 ms", "dom_load_time": "51 ms", "dom_ready_time": "3 ms", "back_end_time": "356 ms", "ssl_time": "71 ms", "front_end_time": "1251 ms", "tcp_time": "20 ms" }


Still need help?

The Atlassian Community is here for you.