Skip to main content
Publishing an incident to a status page shares its details and progress with stakeholders, keeping affected users informed while you work.
Publishing is deliberate, not automatic. An incident attached to a service or functionality on your status page is not published on its own — someone on the response team writes and publishes each update, so every message is reviewed before customers see it.

​
What Gets Published

You can publish incidents to status pages to communicate incident details, timeline updates, and resolution status with your external stakeholders such as customers, partners, or internal teams. When you publish an incident to a status page, it will display:
  • Incident title
  • Affected Services, Functionalities & External Services
  • Timeline of events
  • Incident resolution status
Incident Status Page

​
Publishing From Slack

In addition to using the web interface for publishing incidents to status pages, you can also accomplish the same thing without leaving Slack. To publish an incident using Slack, do the following: From Slack, navigate to the Slack channel specific to that incident, and type the command: /rootly statuspage
Publish an incident using Slack
A dialog will be presented for you to choose the appropriate status pages where you want the incident published. This will also be your chance to add a useful title and description so your external users can better understand. Add the appropriate information in the title and event fields. Select a status for the incident, and then click Publish.

​
Publishing From the Web UI

To publish an incident on a status page in Rootly’s Web UI:
1

Open the Status Page Tab

On the incident’s details page, navigate to the Status Page tab.
2

Publish the Incident

Click Publish Incident, and fill out the form to write your incident update.
3

Use a Template (Optional)

Use any templates provided to help craft and standardize your message.
4

Publish

Once you’ve provided all the details, the incident will be published to the status page.
Publish incident form
Any Service or functionality attached to the incident that is also a component of that status page will be automatically updated to show that it is currently Affected by an incident. Once the status page is updated to indicate that the incident is resolved, the component will be updated to Operational.

​
Updating a Published Incident

As your incident progresses, you’ll need to continually communicate progress to your customers and stakeholders via the status page. You can do so from the same tab in your incident’s detail page.
  1. Click ‘Add to status page’ and fill out the necessary information.
  2. Rootly will pre-fill the title based on the previous update that was published to the status page.

​
Resolving a Published Incident

Once your incident has been resolved, publish your final update to the status page using the same flow above. Make sure to update the status in this form to ‘Resolved’ so that your stakeholders know the issue has been resolved, and all impacted components will return to operational.

Status Pages

The umbrella concept — where published incidents actually show up.

Creating a Status Page

Set up the page before you can publish updates to it.

Incident Timeline

Where published-update events surface inside the incident record.