Disaster Recovery

App service stops working#

Perform these steps when no Hub pages are loading and you are receiving server level errors.

In production, the Hub app service is geo-redundant. The West US instance is used primarily, but if it fails, the East US instance is switched to by the traffic manager.

  1. Navigate to the affected web server app service in the Azure App Portal. See the list of services for links to each
  2. Press Restart and confirm the restart
  3. Wait for the completion of the app service restart and then verify the service is running by opening Hub in the corresponding environment

App not working correctly or not found#

Perform these steps when Hub is working properly but an individual application is not. This the recommended contingency plan when deploying an application.

Apps released through TeamCity#

  1. Navigate to the application's entry in TeamCity
  2. Select Deploy to X where X in the affected environment
  3. Find the artifact used by the previously known working build a note this for later. Eg. #1.6.2.225
    • The artifact build number is noted under the arrow next to x artifact depedency change
  4. Select ... next to Run
  5. Under Dependencies select the artifact previously identified
  6. Select Run Build
  7. Wait for the deployment to finish and then confirm it is working by opening the application in Hub

Apps released through Azure DevOps#

  1. Navigate to the application's entry in Azure DevOps
    • Applications will commonly be under their owning team's project. This can be found in BirdBrain
  2. Select Pipelines > Pipelines
  3. Select the application you want to deploy
  4. Select the previously know working run
  5. Select Rerun stage in the affected environment
  6. Wait for the stage to complete and then confirm it is working by opening the application in Hub

Sidebar is not displaying entries#

Perform these steps when the Hub sidebar has no applications listed in it. This has been cause by an improperly formatted applications.json

  1. Navigate to application.json release pipeline
  2. Select a the most recent known working release
  3. Under the affected environment, select Redeploy
  4. Wait for the deployment to finish and then confirm it is working by opening Hub
Edit this page
Last updated on by Paulo Andrade