Skip to content
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

Merged
merged 5 commits into from
Nov 21, 2024
Merged

Conversation

jimleroyer
Copy link
Member

Summary | Résumé

  1. Upgraded NewRelic to v10.3.0
  2. Disable package reporting for all environments. We get dependency vulnerability detection with renovate and New Relic adds initialization boot up time with that feature, so this is not beneficial for us.

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

  • This PR does not break existing functionality.
  • This PR does not violate GCNotify's privacy policies.
  • This PR does not raise new security concerns. Refer to our GC Notify Risk Register document on our Google drive.
  • This PR does not significantly alter performance.
  • Additional required documentation resulting of these changes is covered (such as the README, setup instructions, a related ADR or the technical documentation).

⚠ If boxes cannot be checked off before merging the PR, they should be moved to the "Release Instructions" section with appropriate steps required to verify before release. For example, changes to celery code may require tests on staging to verify that performance has not been affected.

@jimleroyer jimleroyer self-assigned this Nov 20, 2024
@@ -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 [
Copy link
Member Author

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
Copy link
Collaborator

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?

Copy link
Member Author

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.

Copy link
Collaborator

@sastels sastels left a 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.

@jimleroyer jimleroyer merged commit 7da719b into main Nov 21, 2024
5 checks passed
@jimleroyer jimleroyer deleted the feat/upgrade-new-relic-to-latest branch November 21, 2024 18:52
This was referenced Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants