Update tenant overview with comprehensive status indicators

Loryn Bortinsrequested to merge
update-tenant-status-docs into master

Summary

This MR expands the tenant overview documentation with comprehensive status indicators and maintenance information for GitLab Dedicated instances.

Background

This documentation update supports the Switchboard tenant status feature implementation, which provides different levels of information visibility:

  • Customer view: High-level status indicators (Normal, Degraded Performance, Service Disruption) and maintenance notices
  • Internal GitLab view: Additional detailed incident information from incident.io for support engineers and SREs

Related work: Show active and recent incidents for a tenant in Switchboard

Changes

  • Replaces the brief "Instance status indicators" section with a detailed "Tenant Status" section
  • Adds comprehensive explanations for Normal, Degraded Performance, and Service Disruption states
  • Includes maintenance indicators for scheduled and emergency maintenance
  • Documents what information isn't displayed and important notes about SLA calculations
  • Provides clear guidance for users on what to do in different scenarios
  • Links to related resources for incident severity definitions and maintenance operations

Content Details

The new section includes:

Status Indicators

  • Normal: No active S1/S2 incidents
  • Degraded Performance: Active S2 incidents affecting core functionality
  • Service Disruption: Active S1 incidents with services fully down

Maintenance Indicators

  • Scheduled Maintenance: During planned maintenance windows
  • Emergency Maintenance: During critical, time-sensitive updates

Additional Information

  • What incidents aren't displayed (S3/S4, non-impacting lifecycle stages)
  • Important notes about SLA calculations and sync timing
  • User guidance for different scenarios
  • Links to related documentation

This provides GitLab Dedicated customers with clear, actionable information about their instance status and what to expect in different scenarios, while supporting the broader status visibility initiative that includes enhanced internal tooling for GitLab support teams.

Edited by Loryn Bortins

Merge request reports