Sazabi
Status PagesViewing

Component Details

How to view detailed information about individual status components.

Each component on your status page can be expanded to show detailed information about its current state, history, and uptime statistics.

Expanding a component

Click any component row on the status page to expand its detail view. The expanded view provides comprehensive information about that component's health.

Timeline chart

The expanded component view includes a visual 7-day history.

Visual representation

The timeline shows:

  • Color-coded buckets: Each time segment is colored based on status
    • Green: Operational
    • Yellow: Degraded
    • Red: Outage
  • 7-day range: Full week of history at a glance
  • Time segments: Divided into readable time buckets

Interaction

Hover over any segment in the timeline to see:

  • Exact time range for that bucket
  • Status during that period
  • Duration of any issues

Uptime statistics

Each component displays uptime metrics based on historical data.

7-day uptime percentage

The primary metric shown is the percentage of time the component was operational over the past 7 days.

Calculation

Uptime is calculated as:

Uptime % = (Total time - Outage time) / Total time * 100

The uptime percentage only counts full outages. Degraded periods do not reduce the uptime percentage, though they are visible in the timeline.

Display

  • High uptime: Shown in green (e.g., "99.9%")
  • Reduced uptime: Shown in yellow or red depending on severity
  • Exact percentage: Calculated to one decimal place

Issue list

The detail view shows issues associated with this component.

Active issues

Active issues appear at the top with:

  • Issue severity (degraded or outage)
  • Issue summary
  • Start time
  • Duration (ongoing)

Resolved issues

Below active issues, you will see recently resolved issues:

  • Severity level
  • Summary description
  • Duration (total time from start to resolution)
  • Resolution timestamp

Issues often link to investigation threads. Click through to see the full context of how the issue was discovered and resolved.

Next steps