Sumo Logic Lambda Layer – HTTP / DB Tracing Support

[Ayan189]

Hi Team,

We are currently evaluating AWS Lambda tracing using the Sumo Logic OpenTelemetry Lambda layer and wanted to clarify the expected behavior around HTTP and database tracing when using only the Sumo-provided layer and environment variables.

Current setup:

Region: us-east-2
Lambda runtime: Node.js 20

Layer used:

arn:aws:lambda:us-east-2:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1

Environment variables configured:

AWS_LAMBDA_EXEC_WRAPPER=/opt/otel-handler
OTEL_SERVICE_NAME=otel-by-layer
OTEL_RESOURCE_ATTRIBUTES=application=otel-by-layer,cloud.account.id=xxxxxxxxxx,deployment.environment=dev
OTEL_TRACES_SAMPLER=always_on
SUMO_OTLP_HTTP_ENDPOINT_URL=https://endpoint.com

Observed behavior:

Lambda invocation traces are successfully visible in Sumo Logic.

AWS Lambda–level telemetry and basic AWS service traces are captured as expected.

However, outbound HTTPS calls and database operations are not appearing in traces.

Based on our testing, it appears that Node.js OpenTelemetry auto-instrumentation is not enabled by default when using only the Sumo Logic Lambda layer and environment variables.

Clarification requested:

Does the Sumo Logic OpenTelemetry Lambda layer support automatic tracing of outbound HTTPS calls and database operations for Node.js Lambdas using only the Sumo layer and environment variables?

If yes, are there additional configuration steps or environment variables required to enable HTTP/DB auto-instrumentation?

If no, is it expected that HTTP and database tracing requires explicitly enabling Node.js auto-instrumentations beyond the default Sumo Lambda layer?

We want to confirm whether the observed behavior is expected by design or if we are missing a configuration step when relying solely on the Sumo-provided Lambda layer.

Thanks in advance for the clarification.

Best regards,
Ayan