Your status page will be your first line of communication with your customers in the event something breaks. You can use your status page to notify your customers and those who depend on your service when things are changing, not working as expected, or undergoing maintenance.
There are three primary parts of your status page
Services are the things you want to notify your customers about. Think of what composes your service, each important part should be represented as a service.
For example, you might add your API as a service, or an email service.
If your service is made up of smaller services you can create what we call a subservice. For example, if you have a web application you could create subservices to represent the frontend interface, the database, and the backend API.
An incident represents a problem with one of your services. If your service goes down, or if the quality of service becomes degraded you should create an incident to notify your customers.
As you move towards resolving an issue, you can update your incident with news so your customers stay in the know.
Maintenance notifications let you notify customers of maintenance you will be conducting in the future. If you know your network might be slower than usual because of a switch replacement, consider creating a maintenance notification so your customers know ahead of time.