Component statuses, incident impact, and top-level status all relate with each other. Incident impact depends on the top-level status, and top-level status is calculated based on individual component statuses.
First, let's take a look at component statuses.
Components have a "status". They can include...
Read more about these statuses in the components overview article. If you're using component groups, read about how component groups are calculated and how you can override the status of a component group in the component groups article.
Component statuses affect the top-level status. Let's take a look at "top-level status".
Top-level status is the status displayed at the top of your page. You can think of this as the overall condition your product/service is in. Hopefully your top-level status is “all systems operational” more often than not.
Top-level status can be any of the following...
Top level status gets calculated automatically according to the status of the components on the page. In general, we look at the status of all components on the page and apply the top-level status according to the state the page's components are in. Let's take a closer look at how we calculate this...
For pages with 0 components
Top Level Status will always be All Systems Operational (unless there is an active incident).
For pages with 1 component
For pages with 2 or more components
This is where things get a little trickier. We use the following decision tree logic to calculate top level status:
After every component change, we’ll check to see if top level status needs to be updated. The top-level status will be automatically updated based on the status of the components.
Top-level status influences the "impact" of an incident. Let's take a look at "incident impact".
It's important for your customers to know how severe an incident is. That's why we have “incident impact”. We apply the incident impact based on the most severe top-level status during the incident lifecycle. On the front-end, incident impact shows as a color, which signifies how severe the incident is/was.
The incident impact is dependent on the top-level status. In other words, the top-level status during an incident lifecycle directly affects the “incident impact”.
For example, an incident with a “major” impact will show as red, while an incident with no impact at all will show as black.
Incident impact can be any of the following...
Incident impact is calculated by retaining the most severe top-level status the page had during the lifecycle of the incident. Remember, top-level status is calculated by looking at the status of the components. So, incident impact is indirectly calculated by the state of the components during the incident lifecycle.
Let's take a closer look...
After every component change, we’ll check to see if incident impact needs to be updated.
You can override incident impact by going to the 'incidents' tab > select view incident > hover of the title and click edit > and then select the incident impact you want to set it as.
If you have any questions about this, reach out at firstname.lastname@example.org!