Set up New Relic for Staging and Production #334
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spilth
commented
Jul 23, 2024
| @@ -31,7 +31,9 @@ | |||
| # http://capistranorb.com/documentation/getting-started/configuration/ | |||
| # Feel free to add new variables to customise your setup. | |||
|
|
|||
|
|
|||
| set :default_env, { | |||
There was a problem hiding this comment.
Since RAILS_ENV is to production in both staging and production, I'm using this to override what environment New Relic thinks it is. This will help keep staging and production data separate in New Relic.
spilth
commented
Jul 23, 2024
|
|
||
| common: &default_settings | ||
| # Required license key associated with your New Relic account. | ||
| license_key: <%= Settings.NEWRELIC_LICENSE_KEY %> |
There was a problem hiding this comment.
This is set in the production.yml file on both staging and production.
spilth
commented
Jul 23, 2024
| @@ -1,6 +1,7 @@ | |||
| SECRET_KEY_BASE: 6c51f19b57fdebd3dfd2a3cf8b69fab7f41a529b6bfbf8bff4a85815934066cbe22ddf7fa6083f227288c04e4eeb6c28f0fd90e31fc02314aaceb135dacecc07 | |||
|
|
|||
| DEVISE_SECRET_TOKEN: 2c847492b6d434c808e63a93ff16a7a897aa4c09943edaaf7aa498a29649048113cf55731282e39a82ae7ce3fb9f1087586d474fc483ad6f63806986a5a02a6c | |||
| NEWRELIC_LICENSE_KEY: none | |||
There was a problem hiding this comment.
To avoid putting the license key in Git, I'm setting this to none and disabling monitoring in development.
ekate
approved these changes
Jul 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
We currently have very little insight into the performance of the Spatial Data Repository or the errors that users are encountering. Additionally it's difficult to search/watch logs on the servers due to their size and level of activity.
This is intended to help with #316
Solution
Add and configure New Relic so we can easily view requests, errors, logs and potential issues for our Staging and Production environments.
Note: The
NEWRELIC_LICENSE_KEYkey/value has already been set up in the staging and production environment configuration files on the servers.Type
Chore