Versions Compared

Version Old Version 4 New Version Current
Changes made by

Shivi Sivasubramanian

Shivi Sivasubramanian

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • When an incident is created in Status.io, an alert is created in Jira Service Management automatically through the integration.

  • When an incident is resolved in Status.io, the alert will automatically be closed in Jira Service Management automatically through the integration.

  • When an alert is created in Jira Service Management, an incident is created in Status.io automatically through the integration.

  • When an incident is closed in Jira Service Management, the incident will be resolved in Status.io automatically through the integration.

Set up the integration

...

  1. In Status.io, enable webhook notifications if not already enabled.

  2. Open the "Notifications" tab on the left menu and then , navigate to the Webhook section, and select ON/OFF.

  3. On the Status page, select SUBSCRIBE.

  4. Open the "Webhook" tab from the menu at the top.

  5. Paste the URL you copied while adding the integration in Jira Service Management into the first field.

  6. Enter an email address in the second field.

  7. Select Subscribe.

Expand
titleSetting Containers, Components, State, and Status Information

This step is optional.

Set extra properties of the alert to inform Status.io which containers and components are affected by the incident. These extra properties are added to the "Extra Properties" field of the alert. If "Containers" and "Components" are set as extra properties, an incident is created only for these containers and components on the Status.io side. If no containers or components are selected, the incident is created for all containers and components.

Here is a list of the extra properties that can be set to change the information that is sent to Status.io:

  • Containers (containers that are affected by the incident)

  • Components (components that are affected by the incident)

  • Current Status (current status of the incident)

  • Current State (current state of the incident)

Enter the "Containers" and "Components" properties as IDs. To find the Ids of these containers and components, complete the following steps:

  1. In Status.io, select Infrastructure from the left menu.

  2. Select the Modify button "(>)" of the first item in the Components list.

  3. Select the API tab under the Automatic Status Updates section.

  4. Find the ID of the component and the ID of the container that has the component under that tab.

  5. Repeat the instructions above for each component in the "Components" list to use.

Set the "Current Status" and "Current State" extra properties to set the status and the state of the incident. If "Current Status" and "Current State" extra properties are not set, the incident is created by the default values of the "Current Status" and "Current State", which is 100. Enter the "Current Status" and the "Current State" extra properties as Status Codes.

Incident Status Codes:

  • 100 - Operational

  • 300 - Degraded Performance

  • 400 - Partial Service Disruption

  • 500 - Service Disruption

  • 600 - Security Event

Incident State Codes:

  • 100 - Investigating

  • 200 - Identified

  • 300 - Monitoring

Sample payload sent from

...

Status.io

Expand
titleSample payload in JSON format
Code Block
{
  "id": "57ca879d96a04686040000cc",
  "datetime": "2016-09-03T08:19:41.459Z",
  "current_status": "Degraded Performance",
  "current_state": "Investigating",
  "previous_status": "Security Issue",
  "previous_state": "Monitoring",
  "components": [
    {
      "name": "WebSite2",
      "_id": "57ca82dca530225c6d000085"
    },
    {
      "name": "Website",
      "_id": "57c987f72d8d333607002c3d"
    }
  ],
  "containers":[
    {
      "name": "Container1",
      "_id": "57ca82d0db69d71f40000083"
    },
    {
      "name": "Primary Data Center",
      "_id": "57c987f72d8d333607002c3c"
    }
  ],
  "details": "Details",
  "status_page_url": " https://jsm.status.io",
  "incident_url": "https://jsm.status.io/pages/incident/57c987f72d8d333607002c2d/57ca879d96a04686040000cc"
}

...