Instant notifications with subscriptions
Crucial elements of the best status page
It doesn't matter how your infrastructure or service is built; you can describe it with easy-to-use two-level components.
For example, the parent component could be Database Cluster and the child components node1, node2, and node 3. In another case, the parent component could be a location (New York) and the child components website, database, and firewall.
If you want to show components' historical uptime for your customers, showcase components are the way. Just select the time period that you want, and your chart is ready to go. If you don't want to wait, you can back-fill component history while you create your component in Dashboard.
In Dashboard, you can also customize different colors for uptime percents. For example green for uptime higher than 99% and yellow for uptime higher than 98% but lower than 99%.
There are several states (operational, degraded performance, minor outage, and major outage) that component can be in. Changing the state will have an effect on uptime calculation. Different states have a different impact on the status page - major outage could be seen as red and minor outage as a yellow. Like almost everything else, you can customize these colors in your status page settings.
It is also possible to customize effect for all other states but operational. For example, major outage effect could -100%, partial outage -50%, and degraded performance -20% - it is up to you.
No, your components don't have to be a dummy. It is possible to attach up to five monitors per component. Let's say that you have database cluster (three nodes) and you would like to change its state to degraded performance when two nodes are down, but to major outage when all are down - no problem. Just create a component "Database Cluster" and attach three monitors (node1, node2, and node3) to it.
It is possible to customize following things:
When the crisis strikes, it's important to communicate what the problem is and how is it affecting your customer. By creating an incident and changing its state according to the current situation, you will keep your customer updated. Sometimes the crisis can take a long time, and that is when it is essential to have a clear description of the issue.
The crisis would not probably affect all of your services, and that is when you would like to use components and their states to describe if the crisis affects each part of your services.
Add few incident templates before the crisis occurs, and you can avoid the crisis communication hassle, and focus on fixing the issue.
Maintenances are something that you can't avoid if you are running a business that has IT related environments. Often maintenances will cause an outage even if you didn't expect it to happen, and at least that is the reason why you should tell your customers about upcoming maintenances.
Schedule the maintenance in Dashboard, and it will be shown on the Status Page. Just like the incidents, you attach selected components on each maintenance. It is also possible to choose whether to override component state on Status Page with "under maintenance" state or not.
If you have regular maintenances, you would probably like to save your maintenance as a template for the next maintenance.