Search results for "{{ search.query }}"

No results found for "{{search.query}}". 
View All Results

Atlassian Status Page Integration

Atlassian StatusPage is a status and incident communication tool that helps service providers keep their customers and employees informed during downtime to build trust and cut support costs. Atlassian StatusPage also lets service providers add a component for each of the separate infrastructure or functional part of their service.

​What does OpsGenie offer to Atlassian StatusPage users?

OpsGenie has a powerful two-way integration with Atlassian StatusPage. The integration can be used as follows:

  1. Atlassian StatusPage sends webhook notifications on incident updates. With Atlassian StatusPage Integration, every new incident creates an alert in OpsGenie, and every update of the incident gets added as a Note to the existing alert. OpsGenie acts as a dispatcher for these alerts, determining the right people to notify based on on-call schedules, notifying them using email, text messages (SMS), phone calls and iOS & Android push notifications, and escalating alerts until the alert is acknowledged or closed.
  2. OpsGenie can create an incident in Atlassian StatusPage, if an OpsGenie action is mapped to a create an incident or create incident and update the components'/incident's statuses according to tags Atlassian StatusPage action. OpsGenie can resolve an incident in Atlassian StatusPage, if an OpsGenie action is mapped to a resolve the incident or resolve the incident and update the components' statuses according to tags Atlassian StatusPage action. OpsGenie can update the incident in Atlassian StatusPage, if an OpsGenie action is mapped to an add note to the incident Atlassian StatusPage action.

Functionality of the integration

  • When an incident is created in Atlassian StatusPage, an alert will be created automatically in OpsGenie.
  • When an incident is closed in Atlassian StatusPage, the related alert will be closed automatically in OpsGenie.
  • If Send Alert Updates Back to Atlassian StatusPage is enabled, actions for Atlassian StatusPage will be executed in Atlassian StatusPage when the chosen action is executed in OpsGenie for alerts which are created by the Atlassian StatusPage integration.
  • If Create Atlassian StatusPage Incidents for OpsGenie Alerts is enabled, actions for Atlassian StatusPage will be executed in Atlassian StatusPage when the chosen action is executed in OpsGenie for alerts which have a source other than the Atlassian StatusPage integration.
  • When a specially formatted tag is added to the alert, the statuses of the components/incident in Atlassian StatusPage will be changed to the given status, if an update components'/incident's statuses according to added tags Atlassian StatusPage action is mapped to a tag is added to the alert OpsGenie action.
  • The statuses of the components given in the tags will be changed to Operational, when applicable, if a resolve incident and update components' statuses according to tags Atlassian StatusPage action is mapped to an OpsGenie action.
  • These action mapping features are explained in detail in the Action Mapping Feature section below.

Atlassian StatusPage-to-OpsGenie integration

  1. Please create an OpsGenie account if you haven't done already
  2. Go to OpsGenie Atlassian StatusPage Integration page,
  3. Specify who should be notified for Atlassian StatusPage alerts using the "Teams" field. Auto-complete suggestions will be provided as you type.
  4. Copy the URL by clicking on the copy button or selecting.
  5. Click on "Save Integration".

Configuration in Atlassian StatusPage

  1. In Atlassian StatusPage, go to the "Notifications" interface, open "Settings" tab and enable "Allow webhook subscribers" option.
  2. Click "Save All Changes."
  1. Go to your status page and click "Subscribe To Updates."
  2. Click webhook tab from the subscription dropdown.
  3. Paste to the URL field
  4. Click "Subscribe To Notifications."

OpsGenie-to-Atlassian StatusPage integration

  1. In Atlassian StatusPage, go to "Manage Account" page, and select "API" tab.
  2. Copy the Page ID.
  3. In OpsGenie Atlassian StatusPage integration page, check Send Alert Updates Back to Atlassian StatusPage and/or Create Atlassian StatusPage Incidents for OpsGenie Alerts and paste the page ID into "Atlassian StatusPage Page Id” field.
  4. In Atlassian StatusPage, copy the API key and paste it in OpsGenie into the "Atlassian StatusPage API Key" field.
  1. You can control which type of alerts will be sent to Atlassian StatusPage by using the "Alert Filter".
  2. Save the integration. OpsGenie will attempt to verify the settings with Atlassian StatusPage upon save.

Action Mapping Feature

OpsGenie allows customers to define action mappings between OpsGenie actions and Atlassian StatusPage actions.

For alerts created by Atlassian StatusPage

  • You can use this section to map OpsGenie actions to Atlassian StatusPage actions when the source of the alert is Atlassian StatusPage (i.e When the alert is created by Atlassian StatusPage integration.)
  • You can map different OpsGenie actions to different Atlassian StatusPage actions. For example, you can update the Atlassian StatusPage incident, when a note is added to the OpsGenie alert. In order to do this, you should define If a note is added to the alert in OpsGenie, add note to the incident to the incident in Atlassian StatusPage. mapping in Send Alert Updates Back to Atlassian StatusPage section.

For other OpsGenie alerts

  • You can use this section to map OpsGenie actions to Atlassian StatusPage actions when the source of the alert is NOT Atlassian StatusPage (i.e When the alert is created by another integration.)
  • For this purpose, you can use Create Atlassian StatusPage Incidents for OpsGenie Alerts section. In order to use this functionality, you need to map one OpsGenie action to create an incident or create an incident and update the components'/incident's statuses according to tags Atlassian StatusPage action. The OpsGenie action doesn't have to be alert is created, it can be other actions as well.
  • a tag is added to the alert and a custom action is executed on alert actions differ from other actions. When you select one of these actions, you'll see an extra field to enter for which tags or for which custom action this mapping will work.
  • You can enter multiple tags by separating the tags with a comma. If you enter multiple tags, the mapping will work if the alert has one or more of the specified tags. You can also leave the tags field empty, if you would like the mapping to work for any tag.
  • If you select a custom action mapping, you must specify the name of the custom action that the mapping will work. It cannot be left empty.
  • If you map an OpsGenie action to multiple Atlassian StatusPage actions, you will get an error, except for the a tag is added to the alert and a custom action is executed on alert actions. You can save multiple mappings for these actions, because they will differ by the given tags and the given custom action names.

Changing Component/Incident Statuses via Alert Tags (Optional)

  • You can change the statuses of the components/incident in Atlassian StatusPage by adding some specially formatted tags to the alert.
  • These tags can be added at the creation of the alert or can be added after creating the alert. If you map an OpsGenie action to create an incident and update the components'/incident's statuses according to tags Atlassian StatusPage action, when an alert with specially formatted tags is created in OpsGenie, an incident will be created in Atlassian StatusPage and the statuses of the components and the incident will be changed according to the specially formatted tags. Or if you map an a tag is added to the alert OpsGenie action to an update the components'/incident's statuses according to added tags Atlassian StatusPage action, when a specially formatted tag is added to the alert in OpsGenie, the statuses of the components/incident will be changed according to the added tags.
  • The tags should be formatted as cmp_[component name]:[status] where [component name] is the name of the component that you would like to change its status and [status] is one of the allowed statuses for the component. These allowed statuses are listed below, under the Allowed Component Statuses header.
  • You can change the statuses of multiple components by adding a separate status tag for each component. Please check the examples below.
  • The statuses of the components given in tags will be changed to Operational in Atlassian StatusPage, if you map an OpsGenie action to a resolve the incident and update the components' statuses according to tags Atlassian StatusPage action.

Allowed Component Statuses

  • operational
  • degraded_performance
  • partial_outage
  • major_outage

Allowed Incident Statuses

  • investigating
  • identified
  • monitoring
  • resolved

Examples

  • cmp_API:degraded_performance
  • cmp_Database Server:partial_outage
  • cmp_Management Portal:operational
  • inc:monitoring
  • inc:identified

Sample payload sent from Atlassian StatusPage

{
  "meta":
  {
    "unsubscribe": "https://opsgenietest.statuspage.io/?unsubscribe=8rx45n6txwh3",
    "documentation": "http://doers.statuspage.io/customer-notifications/webhooks/"
  },
  "page":
  {
    "id": "1k9dvd5q1qlv",
    "status_indicator": "none",
    "status_description": "All Systems Operational"
  },
  "incident":
  {
    "name": "incident1",
    "status": "investigating",
    "created_at": "2015-10-08T13:13:53.303Z",
    "updated_at": "2015-10-08T13:13:53.558Z",
    "monitoring_at": null,
    "resolved_at": null,
    "impact": "none",
    "shortlink": "http://stspg.io/1Z1G",
    "postmortem_ignored": false,
    "postmortem_body": null,
    "postmortem_body_last_updated_at": null,
    "postmortem_published_at": null,
    "postmortem_notified_subscribers": false,
    "postmortem_notified_twitter": false,
    "backfilled": false,
    "scheduled_for": null,
    "scheduled_until": null,
    "scheduled_remind_prior": false,
    "scheduled_reminded_at": null,
    "impact_override": null,
    "scheduled_auto_in_progress": false,
    "scheduled_auto_completed": false,
    "id": "hk801ps7x9x4",
    "page_id": "1k9dvd5q1qlv",
    "incident_updates":
    [
      {
        "status": "investigating",
        "body": "this is a test incident",
        "created_at": "2015-10-08T13:13:53.556Z",
        "wants_twitter_update": false,
        "twitter_updated_at": null,
        "updated_at": "2015-10-08T13:13:53.556Z",
        "display_at": "2015-10-08T13:13:53.556Z",
        "id": "7m0y35xlqh8j",
        "incident_id": "hk801ps7x9x4"
      }
    ]
  }
}

Atlassian Status Page Integration