Skip to content

Commit 8c27540

Browse files
docs: require AWS_LAMBDA_EXEC_WRAPPER for manual instrumentation
The Manual Instrumentation steps did not mention AWS_LAMBDA_EXEC_WRAPPER=/opt/wrapper, which is required to enable tracing (it routes the Runtime API through the extension so spans can be correlated to the current invocation and enriched). Without it, traces are discarded with "no invocation IDs" unless every exported span already carries a faas.invocation_id. Add it as an explicit step. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent 190b609 commit 8c27540

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

README.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -125,9 +125,10 @@ The following environment variables allow fine-grained control over secret maski
125125
If you prefer to set up OpenTelemetry instrumentation yourself instead of relying on the extension's auto-instrumentation, you can use the manual layer and point your OTLP exporters to the extension's local endpoint. The extension will receive the telemetry, enrich it, and forward it to Dash0.
126126

127127
1. Add the manual layer to your Lambda function: `arn:aws:lambda:<region>:115813213817:layer:dash0-extension-manual:<version>`.
128-
2. Configure your OTLP trace exporter to send to `http://127.0.0.1:9009/v1/traces`.
129-
3. If exporting metrics, configure your OTLP metric exporter to send to `http://127.0.0.1:9009/v1/metrics`.
130-
4. Make sure to flush all telemetry before the Lambda invocation completes (e.g., in a response hook or before returning the response).
128+
2. Set `AWS_LAMBDA_EXEC_WRAPPER=/opt/wrapper`. This is **required** (see [Required](#required)) for the extension to correlate spans to invocations and enrich them (trigger, payloads, cold-start/overhead metrics). Without it, traces are discarded with `[DASH0] /v1/traces has no invocation IDs, discarding trace` unless every exported span already carries a `faas.invocation_id` attribute.
129+
3. Configure your OTLP trace exporter to send to `http://127.0.0.1:9009/v1/traces`.
130+
4. If exporting metrics, configure your OTLP metric exporter to send to `http://127.0.0.1:9009/v1/metrics`.
131+
5. Make sure to flush all telemetry before the Lambda invocation completes (e.g., in a response hook or before returning the response).
131132

132133

133134
## Enrichment Attributes

0 commit comments

Comments
 (0)