-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgraded NewRelic to v10.3.0 #2367
Conversation
@@ -16,7 +17,7 @@ | |||
# Guincorn sets the server type on our app. We don't want to show it in the header in the response. | |||
gunicorn.SERVER = "Undisclosed" | |||
|
|||
on_aws = os.environ.get("NOTIFY_ENVIRONMENT", "") in [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know why we fell back on an empty string instead of the default None
value. It seems unnecessary considering the following condition with the AWS env check.
@@ -7,7 +9,8 @@ | |||
|
|||
from app.aws.xray.context import NotifyContext | |||
|
|||
newrelic.agent.initialize() # noqa: E402 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Strange that we weren't giving it an environment
before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, we should have done that before. We didn't always have a newrelic.ini file though. Not having the env passed means that specific config found in the newewlic.ini would be ignored, but the generic section would still be applied.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just one confuzed question.
Summary | Résumé
Related Issues | Cartes liées
Test instructions | Instructions pour tester la modification
Monitor deployment in the staging environment and make sure this is not going in a crash loop with the kubernetes pods.
Release Instructions | Instructions pour le déploiement
Monitor deployment in the staging environment and make sure this is not going in a crash loop with the kubernetes pods.
Reviewer checklist | Liste de vérification du réviseur