Skip to content

Mop for Region-based Status Page Deployment

1. Change Overview

Deploy the Region-based Status Page feature to the production environment.

This release introduces:

  • Region-based component availability
  • Region-aware incident and maintenance display
  • Support for unavailable regions per component

2. Preconditions

Before starting the deployment:

  • Customer has been notified of the maintenance window
  • Backup Elastic Beanstalk environment is prepared for rollback
  • ServiceNow change request is approved
  • Configuration added for both Virginia and California:
    • /gss/{env}/gss-service.regions

3. Deployment Steps

3.1 Deploy to California Region(backup)

  1. Deploy Database Changes and Backend Service: run the Jenkins pipeline to deploy
  2. Health check for service: https://service-status-us-west-1.webex.com/ping and https://service-status-us-west-1.webex.com/customer/dashServices/891
  3. Deploy Frontend California: run the Jenkins pipeline to deploy
  4. Validation: Check if it works: https://us-west-1.globalservicestatus.com

3.2 Deploy to Virginia Region

  1. Deploy Database Changes and Backend Service: run the Jenkins pipeline to deploy
  2. Health check for service: 1. for us-east-1 service: https://service-status-us-east-1.webex.com/ping and https://service-status-us-east-1.webex.com/customer/dashServices/891 2. for active region with https://service-status.webex.com/ping (should be us-east-1) 3. for service: https://service-status.webex.com/ping and https://service-status.webex.com/customer/dashServices/891
  3. Deploy Frontend Virginia: run the Jenkins pipeline to deploy
  4. Validation: 1. Check the current region: https://service-status.webex.com/ping 2. Health check for service: https://service-status.webex.com/customer/dashServices/891 3. Check if it works: https://us-east-1.globalservicestatus.com and https://status.webex.com

4. Post Deployment Configuration

After the new version is deployed, perform the following configuration updates.

4.1 Configure Component Unavailable Regions

If a component has unavailable regions, manually update the component configuration via the Component Edit page: Global Service Status , should sync on California site: https://us-west-1.globalservicestatus.com

4.2 Update Existing Incidents

If any Incidents already exist in production, update them to include:

  • Affected Regions
  • Impacted Components

This ensures the incidents display correctly on the region-based status page. It should sync on California site: https://us-west-1.globalservicestatus.com

4.3 Update Existing Maintenances

Option 1 (Recommended)

Populate Regions and the new MaintenanceComponents field to display components as Under Maintenance. It should sync on California site: https://us-west-1.globalservicestatus.com

Option 2

Leave the field empty to maintain the previous behavior (components with under maintenance status will not be displayed).

4.4 Update External Components

If any External Components with non-operational status exist:

  • Set their status = Operational
  • Ensure the following fields are populated if applicable:
    • link
    • description
    • helpLink
    • unavailableRegions

These updates can be performed via Bruno API. It should sync on California site: https://us-west-1.globalservicestatus.com

5. Verification Checklist

After deployment and configuration, verify:

  • Status page loads successfully
  • Region-based filtering works correctly
  • Incidents display correct regions
  • Maintenance displays correct components
  • Component availability is correct per region
  • No errors in backend logs

6. Rollback Plan

If a critical issue occurs:

  1. Switch traffic to the backup Elastic Beanstalk environment.
  2. Restore the previous frontend version if required.
  3. Verify that the previous status page functions normally.

7. Post-Release Tasks

  1. Add the Release Note.
  2. Notify stakeholders that the deployment is complete.
  3. Close the ServiceNow Change Request.