Emergency Runbook

This site is hosted on AWS Amplify and is maintained / supported by New Relic's Developer Experience team. If you have any questions or comments, feel free to create an issue or reach out to us at [email protected].

Helpful links

• Troubleshooting dashboard
• #help-dev-experience (for engineering requests)
• #documentation (for content requests)
• Alert policy
• Architecture diagram (TODO: add link when #823 has been completed)

Troubleshooting

Scenario	Severity	Resolution
Site is not loading	❗ High	Rollback a release
Functionality is broken	⚠️ Medium	Rollback a release
Alert has been triggered	⚠️ Medium	Respond to an incident
Copy needs to be adjusted	👀 Unknown	Create an issue or ping @hero in #documentation

Rollback a release

If the site is not loading, or a piece of functionality is broken, you may will likely need to rollback to a stable release using the following steps:

1. To do.

Respond to an incident

The following steps are for on-call engineers working at New Relic:

1. Don't panic, you've got this!
2. Check to see if there is already an ongoing incident in #emergency-room (or one of the supplemental rooms).
3. If there is not an ongoing incident, start one by following the steps in the Incident Commander Runbook.
4. Refer to the troubleshooting dashboard to get an idea for what could be going on.
5. Look at the recent deployments to production to identify a PR that can be reverted.