Skip to content

Emergency Runbook

jbeveland27 edited this page Jun 9, 2020 · 18 revisions

opensource.newrelic.com runbook

This site is hosted on AWS Amplify by New Relic's OpenSource team and is maintained and supported by New Relic's developer experience team. If you have any questions or comments, please reach out to opensource@newrelic.com.

Alerts

Alerts

To diagnose a particular alert, we've started a Common Issues

CI/CD

This site is deployed utilizing Github Actions for continuous integration (CI) combined with AWS Amplify's branch-based continuous deployment (CD).

Trigger a deployment

Deployments are exclusively handled through merging a PR into the master branch. If an ad-hoc deployment is required, please reach out to a project maintainer.

Rollback a release

Environments

This project supports three environments, local development, staging (a.ka. development), and production.

Note: When building the site, Gatsby coerces anything you've set in NODE_ENV to production

Production

Corresponds to the master branch

New Relic Domains: https://opensource.newrelic.com

New Relic Browser monitoring

Staging (Development)

Corresponds to the develop branch

Amplify Domain: https://develop.d2pwh5nf8rvczf.amplifyapp.com/ New Relic Domains:

New Relic Browser monitoring

Local Development

To run, execute npm start from the root of this repository.

Should you want New Relic Browser instrumentation while developing locally, you will need to add an additional configuration option to gatsby-config.js for the gatsby-plugin-newrelic plugin.

Architecture

The site is a combination of template-generated pages and single pages built using React, markup, and MDX.

Beyond the CI/CD automation, GitHub Actions are used to keep the stats data related to each project updated on a scheduled basis. Some of the architecture consequences of that change are described here.

Common Issues

No issues yet!

Clone this wiki locally