/
Update an incident on Status Page

Update an incident on Status Page

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

What is the purpose of this document?

  • You will understand how to update an 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

Updating 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 navigation and click on “Update” next to the incident for which you need to post an update for, on the Status Page.

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

    • Select the Incident Status from the options available:

      • Investigation

      • Identified

      • Monitoring

      • Resolved

    • Write the update message in the “Message” field

      • For Investigation status - You are also able to give a re-update for the existing status.

      • For Identified Status - This status is to be used when you have identified the cause of the problem and are ready to apply the fix.

        • Example: We continue to work on resolving the issue with Automation for Jira in which rules are not being triggered. We have identified the root cause and expect recovery shortly.

      • For Update Status - Select the “Investigating” status in this case. This is to be used when you want to provide an update not related to any specific status from the statues available.

        • Example: We have implemented some changes due to which new rule executions should now be working without any delays. We continue to work on clearing up the backed up items in the queue

      • For Monitoring Status - This status is to be used when you have resolved the issue but it is in the testing stage(i.e. the issue is being tested on the staging environment).

        • Example: We have identified the root cause of the access issues with Jira and have mitigated the problem. We are now monitoring closely.

      • For Resolved Status - This status is to be used when you have completely resolved the issue on the production/live environment.

        • Example: Between September 30th 12:55 IST to October 1st 02:00 IST, we experienced delays processing triggers for Automation for Jira. The issue has been resolved and the service is operating normally. Change the Component Status to “Operational” in this case.

  • Click on Update and the incident will be updated on the Status Page.

Related content