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

Veneur does not like New Relic Insert Key config #938

Open
andrelop opened this issue May 20, 2022 · 0 comments
Open

Veneur does not like New Relic Insert Key config #938

andrelop opened this issue May 20, 2022 · 0 comments

Comments

@andrelop
Copy link

andrelop commented May 20, 2022

We are trying to evaluate Veneur, specially Venur New Relic sink to send metrics to our New Relic account.
We are trying to use Veneur under Kubernetes as a deployment. The relevant config is basically :

        env:
        - name: VENEUR_NEWRELICACCOUNTID
          value: "<our account id here>"
        - name: VENEUR_NEWRELICINSERTKEY
          value: "<our insert key here>"
        - name: VENEUR_DEBUG
          value: "true"

However, whenever we try to start one pod using the configuration above, we get the following error on Veneur's pod logs :

time="2022-05-20T21:37:22Z" level=info msg="started New Relic sink" accountID=<our account id here> eventType=veneur metric_sink=newrelic serviceCheckEventType=veneurCheck
time="2022-05-20T21:37:22Z" level=info msg="Creating SignalFx sink signalfx" endpoint_base="https://ingest.signalfx.com" metric_sink=signalfx
time="2022-05-20T21:37:22Z" level=fatal msg="Could not initialize server" error="1 error(s) decoding:\n\n* error decoding 'insert_key': invalid type map[string]interface {}"

We tried using old insert keys, generating new ones, tried using insert keys and license keys, bit we are always getting this same error.

We are using Veneur version 14.2.0, more precisely the container image stripe/veneur:14.2.0.

Is there a know way to fix this issue ?

Also, on New Relic docs, a insert key seems to be not recommended anymore. They seem to recommend using a license key instead.

Do you have plans on supporting license keys instead of insert keys ?

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

No branches or pull requests

1 participant