/
Create an incident on Status Page

Create an incident on Status Page

Owned by Akshay Aggarwal (Unlicensed)
Last updated: Oct 20, 2020
3 min read

What is the purpose of this document?

  • You will understand how to create a new incident on the Status Page

Audience

  • On-call Persons

Before you start:

  • You must have access to create and update incidents on Status Page

  • You must have access to the project to which the reported issue might concern with

Creating an Incident:

  • Go to ”https://manage.statuspage.io/login” and log in with the credentials provided to you.

  • Go to Incidents from the options in the toolbar on the left and click on “Create incident”

  • You will be redirected to a page as shown below:

      • Specify the title in the field, “Incident name”

      • Select the Incident status as “Investigating”. This will always be the first status of the incident.

      • Write a brief description of the incident (2-3 lines) in the “Message” field

        • Start with “We are investigating an issue with…”

      • Select the component that this issue is affecting from the list of available components. The available components are:

        • Customer Portal: This component will be affected if there is an issue related to Post Order Experience.

        • Eshopbox Workspace: This component will be affected if there is an issue related to Unicommerce Sync or Algolia Sync.

        • Eshopbox APIs: This component will be affected if there is an issue related to Products and Inventory, Orders and Returns, Payments, Consignments or Platform (Core, Activities, Fulfillment Center, Sales channels, Contacts, Authentication, Dashboard. Jobs)

        • Eshopbox APPS: This component will be affected if there is an issue related to Myntra PPMP or Amazon Prime.

      • After you have selected the component affected, you will be required to select the current state of the component.

      • To communicate the state of each component, you will always have one of the following five statuses:

        • Operational

        • Under maintenance

        • Degraded performance

        • Partial outage

        • Major outage

        Component states are set when creating or updating incidents on your page.

  • Now, Click on “Create” to create the incident.

For Example:

  • Incident Name: Automation for Jira rules are not being triggered

  • Message body: We are investigating an issue with Automation for Jira in which rules are not being triggered, this is impacting all Jira Cloud customers. We will provide more details within the next few hours.

Component statuses

  • Operational

    • Operational means exactly what it sounds like. The component is functioning as expected and in a timely manner.

  • Under maintenance

    • Under maintenance means the component is currently being worked on and is suffering a downtime.

  • Degraded performance

    • Degraded performance means the component is working but is slow or otherwise impacted in a minor way. An example of this would be if you were experiencing an unusually high amount of traffic and the component was taking longer to perform its job than normal.

  • Partial outage

    • Components should be set to partial outage when they are completely broken for a subset of customers. An example of this would be if some subset of customer's data lived in a specific data center that was down. The component might be broken for that subset of customers but is working for the rest and thus there is a partial outage.

  • Major outage

    • Components should be set to major outage when they are completely unavailable.

Related content