-
Notifications
You must be signed in to change notification settings - Fork 54
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
Error: Invalid value for New Relic Account ID #227
Comments
Steps to Reproduce altered from what I put there |
i have the same problem...:( using latest 0.7.2 version of the package. |
I figured it out...the --nr-api-key should be an API key of type "USER". I was using type "INGEST - LICENSE", which didn't work. |
Do we have any updates on this bug yet? Me and my colleagues are facing the exact issue using either USER or INGEST - LICENSE key. |
UPDATE: Never got this working in the end so we're going with Datadog instead; it works out of the box. The key being used in the command is the USER key and it still doesn't work...
|
It worked for me by creating a new USER API key. The error is misleading since the Account ID error message is incorrect, it's the API key that was the issue. |
had the same problem, for me the fix was to use |
NOTE: # Error: Invalid value for New Relic Account ID: Could not retrieve license key from New Relic. Check that your New Relic Account ID is valid and try again.
Description
NOTE: # Error: Invalid value for New Relic Account ID: Could not retrieve license key from New Relic. Check that your New Relic Account ID is valid and try again.
TIP: # The error message is totally misleading. The actual issue was the key was not one expected by the service.
Overall this step looks unnecessary, a user can provide their license key the same way as account id and the user key
Steps to Reproduce
NOTE: # newrelic-lambda integrations install --nr-account-id --nr-api-key
Expected Behaviour
NOTE: # Error: Invalid value for --nr-api-key. It should be your user key, which you can find here https://one.newrelic.com/api-keys
Relevant Logs / Console output
Your Environment
TIP: # AWS EC2 amazon linux
Additional context
The text was updated successfully, but these errors were encountered: