External and Internal service Status Pages
Co
Last updated
Co
Last updated
A Status Page is a communication tool designed to keep users informed about outages and scheduled maintenance. It helps maintain transparency and trust by providing timely updates.
Builds trust with customers by keeping them informed about service status.
Reduces support requests by proactively communicating incidents, reducing repetitive queries.
Improves the incident communication process by structuring how outages and updates are shared.
The Internal Status Page enables admins to add incidents and allows team members to view downtime or ongoing maintenance within the organization.
The Calendar View provides a 90-day incident update with a color-coded system to represent service status:
🟢 Green – No incidents reported, no downtime.
🟡 Yellow – Incidents reported, highest severity is medium.
🔴 Red – High or critical severity or if there is an active downtime.
2. Adding a Service
Why is adding a service important?
Services represent different application endpoints that need monitoring. If a service experiences downtime, the respective application service team can address the issue effectively.
How to Add a Service:
Enter the Service Name
Select the Application Service Name
If an endpoint is associated with the selected service, it will appear in the dropdown.
Click on "Add"
The service will now be displayed in the block view below, showing the 90-day (customizable to 30 or 60 days) stats with a color-coded system:
🟢 Green – No downtime, no incidents reported.
🟡 Yellow – Incidents reported with medium severity or uptime between 100-99%.
🔴 Red – High or critical severity or if there is an active downtime.
Indicator Marks:
Red Cross Mark – Indicates that there is a downtime or an incident reported on the current day.
Green Check Mark – Indicates that there is no downtime and no incidents reported on the current moment.
Admins can create incidents easily using the "Create Incident" button.
Steps to Create an Incident:
Enter Incident Title (e.g., Database Maintenance).
Select Incident Severity (Critical, High, Medium, Low).
Choose Affected Components
These are the services added earlier.
This is optional, as sometimes an entire website may be down.
Provide an Incident Description.
Set Incident Status:
Investigating
Identified
Monitoring
Resolved
Update Message:
The system generates an automatic message, but it can be modified.
Publish the Incident.
Admins can control whether the Status Page is publicly visible or restricted to internal users. This ensures flexibility in how incidents and downtime updates are shared. Admins can choose to publish or un-publish the status page for external users.
Navigate to Admins > Manage Organization
Scroll down to find the "Status Page Settings" toggle
Switch the toggle ON to publish the status page
Switch the toggle OFF to restrict the status page to internal users only
Ongoing Incidents:
New incidents appear in the ongoing incidents list.
Status updates (e.g., Investigating → Identified → Monitoring → Resolved) are reflected in real-time.
Past Incidents:
Once an incident is marked as Resolved, it moves to the Past Incidents section.
It retains all details, including start time, updates, and resolution status.
