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

Upgrade to latest New Relic version #1999

Merged
merged 5 commits into from
Nov 21, 2024
Merged

Conversation

jimleroyer
Copy link
Member

Summary | Résumé

Upgrade to latest New Relic version and bringing additional changes that were performed on the API side.

  1. Upgrade to New Relic v10.3.0.
  2. Pass in environment to New Relic init so that it can get proper environment configuration defined in the newrelic.ini file.
  3. Added a total running timer for the Gunicorn process.
  4. Increased gunicorm hard timeout to 90 seconds.
  5. Disable New Relic package reporting feature as we already have renovate to detect vulnerabilities and this is not worth the feature which adds a lot more time to startup (20+ seconds).
  6. Added fzf command line utility to the devcontainer along with proper shell config.

Test instructions | Instructions pour tester la modification

Check the kubernetes admin pods startup to make sure that these do not get into a crash loop. It is possible we might have to align the admin k8s liveness, readiness and startup probes with the ones in API with their latest changes.

#
# Kubernetes config:
# https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/
graceful_timeout = 85

Check notice

Code scanning / CodeQL

Unused global variable Note

The global variable 'graceful_timeout' is not used.
# Kubernetes config:
# https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/
graceful_timeout = 85
timeout = 90

Check notice

Code scanning / CodeQL

Unused global variable Note

The global variable 'timeout' is not used.
@@ -20,10 +22,34 @@
# to be larger than the idle timeout configured for the load balancer.
# > By default, Elastic Load Balancing sets the idle timeout value for your load balancer to 60 seconds.
# https://docs.aws.amazon.com/elasticloadbalancing/latest/application/application-load-balancers.html#connection-idle-timeout
on_aws = os.environ.get("NOTIFY_ENVIRONMENT", "") in ["production", "staging", "scratch", "dev"]
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.

Copy link

Copy link
Contributor

@ben851 ben851 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jimleroyer jimleroyer merged commit 5285120 into main Nov 21, 2024
11 checks passed
@jimleroyer jimleroyer deleted the feat/upgrade-new-relic-to-latest branch November 21, 2024 19:51
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