External and Internal service Status Pages

What is a Status Page?

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.

Key Benefits of Using a Status Page

• 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.

Temperstack Internal Status Page

The Internal Status Page enables admins to add incidents and allows team members to view downtime or ongoing maintenance within the organization.

Status Page Management Sections

1. Calendar View

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:

1. Enter the Service Name

2. Select the Application Service Name

3. If an endpoint is associated with the selected service, it will appear in the dropdown.

4. Click on "Add"

5. 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.

3. Creating an Incident

Admins can create incidents easily using the "Create Incident" button.

Steps to Create an Incident:

1. Enter Incident Title (e.g., Database Maintenance).

2. Select Incident Severity (Critical, High, Medium, Low).

3. Choose Affected Components

• These are the services added earlier.

• This is optional, as sometimes an entire website may be down.

1. Provide an Incident Description.

2. Set Incident Status:

• Investigating

• Identified

• Monitoring

• Resolved

1. Update Message:

• The system generates an automatic message, but it can be modified.

1. Publish the Incident.

3. Publish Settings

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.

How to Enable the Status Page:

1. Navigate to Admins > Manage Organization

1. Scroll down to find the "Status Page Settings" toggle

2. Switch the toggle ON to publish the status page

3. Switch the toggle OFF to restrict the status page to internal users only

Incident Tracking

• 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.