Node.js autoinstrumentation not working in Node.js 24 Lambda runtime

[garysassano]

After upgrading to the new Node.js 24 Lambda runtime (announced here), OpenTelemetry autoinstrumentation has completely stopped working. The Lambda functions execute successfully, but no telemetry data is being collected or exported.

Environment

• Lambda Runtime: nodejs24.x
• ADOT Lambda Layer: arn:aws:lambda:eu-central-1:901920570463:layer:aws-otel-nodejs-arm64-ver-1-30-2:1

Expected Behavior

OpenTelemetry autoinstrumentation should continue to work with the Node.js 24 runtime, collecting and exporting traces, metrics, and logs as it did with previous Node.js runtimes (18.x, 20.x, 22.x).

Actual Behavior

After upgrading to nodejs24.x:

• Lambda functions execute without errors
• No telemetry data is collected
• No traces appear in configured backends
• Autoinstrumentation appears to be completely inactive

Steps to Reproduce

1. Create a Lambda function with Node.js 24 runtime (nodejs24.x)
2. Attach the OpenTelemetry Lambda layer
3. Configure the required environment variables for autoinstrumentation
4. Invoke the Lambda function
5. Check the telemetry backend for traces/metrics - none appear

It's possible that changes in the runtime environment are causing compatibility issues with the current autoinstrumentation approach.

Possible Causes

• Changes in Lambda initialization lifecycle
• Module resolution changes in Node.js 24
• AWS Lambda wrapper changes
• Environment variable handling differences

Workaround

Currently no known workaround. Staying on Node.js 22.x runtime maintains autoinstrumentation functionality.

[wpessers]

Hi @garysassano, you say you are using ADOT layers. Which is a separate project: https://github.com/aws-observability/aws-otel-lambda

[garysassano]

@wpessers I switched from ADOT to OTel and was able to reproduce the bug, which confirms the issue originates upstream.

Specifically, I switched from:

• arn:aws:lambda:eu-central-1:901920570463:layer:aws-otel-nodejs-arm64-ver-1-30-2:1

To:

• arn:aws:lambda:eu-central-1:184161586896:layer:opentelemetry-nodejs-0_17_0:1
• arn:aws:lambda:eu-central-1:184161586896:layer:opentelemetry-collector-arm64-0_18_0:1

[wpessers]

My bad, this 0.17.0 version of the lambda layer is indeed problematic due to a transitive dependency upgrade. See: open-telemetry/opentelemetry-js-contrib#3219
I've since narrowed down the issue to changes to module resolution behaviour, hoping to get a fix out soon. Will update here as well!

[RaphaelManke]

The issue is that AWS removed the callback support from the handler.
https://aws.amazon.com/blogs/compute/node-js-24-runtime-now-available-in-aws-lambda/

In particular, callback-based function handlers are no longer supported.

{
  "errorType": "Runtime.CallbackHandlerDeprecated",
  "errorMessage": "ERROR: AWS Lambda has removed support for callback-based function handlers starting with Node.js 24. You need to modify this function to use a supported handler signature to use Node.js 24 or later. For more information see https://docs.aws.amazon.com/lambda/latest/dg/nodejs-handler.html.",
  "trace": [
    "Runtime.CallbackHandlerDeprecated: ERROR: AWS Lambda has removed support for callback-based function handlers starting with Node.js 24. You need to modify this function to use a supported handler signature to use Node.js 24 or later. For more information see https://docs.aws.amazon.com/lambda/latest/dg/nodejs-handler.html.",
    "    at errorOnDeprecatedCallback (file:///var/runtime/index.mjs:617:11)",
    "    at createRuntime (file:///var/runtime/index.mjs:1222:5)",
    "    at async ignition (file:///var/runtime/index.mjs:1637:21)"
  ]
}

https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/packages/instrumentation-aws-lambda
needs to be updated I guess.

For me the whole lambda crashes :(

Steps to reproduce

• Got to lambda console and create a new empty lambda with Nodesjs24

• add the layer eg.

  • arn:aws:lambda:eu-central-1:184161586896:layer:opentelemetry-nodejs-0_17_0:1

• invoke it with the test button

• see the error

[maxday]

Thanks @garysassano and @RaphaelManke and @wpessers

I can confirm that we are able to reproduce it and we're working on a fix.
Thanks

[wpessers]

@RaphaelManke that is an issue as well indeed, but seems like a different issue then what @garysassano describes as his lambdas still seemed to work? I see that in the meantime @maxday has also responded, I think we actually discussed that callback style handler issue before in slack so good to have that on the radar again!

[maxday]

We can close as https://github.com/open-telemetry/opentelemetry-lambda/releases/tag/layer-nodejs%2F0.18.0 is released