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

Error: Invalid value for New Relic Account ID #227

Open
4demos opened this issue Dec 16, 2022 · 7 comments
Open

Error: Invalid value for New Relic Account ID #227

4demos opened this issue Dec 16, 2022 · 7 comments
Labels
bug Something isn't working

Comments

@4demos
Copy link

4demos commented Dec 16, 2022

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

  • ex: Browser name and version:
  • ex: Operating System and version:

Additional context

@4demos 4demos added the bug Something isn't working label Dec 16, 2022
@4demos
Copy link
Author

4demos commented Dec 16, 2022

Steps to Reproduce altered from what I put there
newrelic-lambda integrations install --nr-account-id valid-account-id --nr-api-key whatever except the user key

@sloppycoder
Copy link

i have the same problem...:(

using latest 0.7.2 version of the package.

@sloppycoder
Copy link

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.
The error message is kinda misleading. The problem is the API key not the account id.

@risetarnished
Copy link

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.

@knxrb
Copy link

knxrb commented Oct 3, 2023

UPDATE: Never got this working in the end so we're going with Datadog instead; it works out of the box.

Same issue for me as well, trying to set things up to see if New Relic is worth paying for the engineering team to use and I hit this... Is this actively maintained at all? If not, then I need to be spending my time on an alternate product.

The key being used in the command is the USER key and it still doesn't work...

Retrieving integration license key
Usage: newrelic-lambda integrations install [OPTIONS]
Try 'newrelic-lambda integrations install --help' for help.

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.

@mintavenger
Copy link

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.

@tclass
Copy link

tclass commented Mar 20, 2024

had the same problem, for me the fix was to use --nr-region eu it probably used us as default but returned the error that the key is wrong 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. very misleading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants