-
Notifications
You must be signed in to change notification settings - Fork 51
Error "datadog:api key not configured" even though apiKeySecretArn is set #246
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
Comments
Hi @philipwigg - thanks for reaching out! We did just release a fix for this, but looking at your reported plugin version - that fix should be in your deployed runtime. (landed in 4.1.1). Would you mind confirming for me that the version of the Datadog NodeJS Lambda Layer is 74 or greater? Thanks! |
I'm not sure how to check the Lambda layer version, how do I do that? I wonder if maybe |
Hi @philipwigg! The easiest way is to log into the AWS console, go to the Lambda function, and then inspect the Thanks! |
Okay thanks - I'll look into this and get back to you! |
Hi @philipwigg - there are a few things occurring here. It appears that This is only relevant to you if you're using We need to make several additional changes to support |
Expected Behavior
If I have
apiKeySecretArn
configured and the plugin is able to read the DD API key, I do not get an error in the logs complaining thatActual Behavior
I do receive an error that
datadog:api key not configured, see https://dtdg.co/sls-node-metrics
even though I don't need it to be configured because I'm using
apiKeySecretArn
as an alternative.Specifications
The text was updated successfully, but these errors were encountered: