-
Notifications
You must be signed in to change notification settings - Fork 150
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
OOM on API Key change #1428
Labels
3
Story Point Estimate
bug
Something isn't working as designed/intended
oct-dec qtr
Represents proposed work item for the Oct-Dec quarter
Comments
kford-newrelic
added
estimate
Issue needing estimation
3
Story Point Estimate
and removed
estimate
Issue needing estimation
labels
Aug 9, 2023
@agustiza can you confirm : when you did the key rotation, was the new key a valid or invalid key? |
I'm not 100% sure but I think it was a purposedly invalid key. Should be around 25-26th April 2023. |
kford-newrelic
added
the
oct-dec qtr
Represents proposed work item for the Oct-Dec quarter
label
Sep 15, 2023
github-project-automation
bot
moved this from Needs Review
to Code Complete/Done
in Java Engineering Board
Nov 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
3
Story Point Estimate
bug
Something isn't working as designed/intended
oct-dec qtr
Represents proposed work item for the Oct-Dec quarter
Description
Running inside docker containers.
We recently had an API key rotation for the new relic agent on our non productive environments as a way to save costs by disabling monitoring and logging.
We suddenly found out that we were having constant OOMs. Troubleshooting a bit we found out that the culprit was the New Relic Agent.
Sadly I cannot share a reproducible project.
Troubleshooting or NR Diag results
Steps to Reproduce
Very little I can share but it's pretty standard setup.
Your Environment
Docker container using openjdk:8-jre-alpine openjdk:8-jdk-alpine
Current New Relic Agent version
The text was updated successfully, but these errors were encountered: