net/http: invalid header field value for "X-License-Key"

[alexismoreau]

Hello,

Following newrelic/node-newrelic#2905 ; it has stopped working after switching from cross-fetch package to native NodeJS fetch.

I have now the following error :
[NR_EXT] Telemetry client error: Post "https://cloud-collector.newrelic.com/aws/lambda/v1": net/http: invalid header field value for "X-License-Key", payload size: 1922 bytes

I see the function invocations in new relic and regenerated new Ingest license keys but it's still not sending fetch related logs.

Minimal reproduction :

export const handler = async (event, lambdaContext, callback) => {
    console.log({ event, lambdaContext, callback });
    const fetchResult = await fetch('https://api.github.com');
    const body = await fetchResult.json();
    console.log('Fetched from GitHub:', body);
    return {};
};

AWS Lambda running on Node 22, using layer arn:aws:lambda:eu-west-1:451483290750:layer:NewRelicNodeJS22X:8, handler newrelic-lambda-wrapper.handler

Env variables :

NEW_RELIC_ACCOUNT_ID | xxxxxxx
NEW_RELIC_EXTENSION_LOG_LEVEL | DEBUG
NEW_RELIC_EXTENSION_SEND_EXTENSION_LOGS | false
NEW_RELIC_EXTENSION_SEND_FUNCTION_LOGS | false
NEW_RELIC_LAMBDA_EXTENSION_ENABLED | true
NEW_RELIC_LAMBDA_HANDLER | server.handler
NEW_RELIC_LICENSE_KEY | xxxxxxx
NEW_RELIC_TRUSTED_ACCOUNT_KEY | xxxxxxx
NEW_RELIC_USE_ESM | true

Cloudwatch logs :

Can you check on your side ?

Thanks,

[workato-integration]

https://new-relic.atlassian.net/browse/NR-363232

[mrickard]

@alexismoreau Sorry to see you're still having trouble here. The Node agent doesn't send any telemetry to New Relic in serverless mode; that's done by the New Relic Lambda Extension (as shown in the [NR_EXT] log line). You may want to double-check what you're using as the value for NEW_RELIC_LICENSE_KEY. I'd suggest opening a case with Support, who can make sure that the configuration values are correct for your account.

[workato-integration]

https://new-relic.atlassian.net/browse/NR-363685