Dash0 Raises $110M Series B at $1B Valuation

Last updated: July 13, 2026

About AWS Lambda Monitoring

Monitor AWS Lambda functions with auto-instrumentation, synthetic timeout traces, and cold start analysis.

Lambda functions can be instrumented either with the Dash0 Lambda Extension (via the UI auto-instrumentation flow or by adding the layer manually via the Dash0 Lambda Extension repository) or with generic OpenTelemetry instrumentation using the OpenTelemetry SDK directly in your function code.

The Dash0 Lambda Extension automatically captures traces, logs, and metrics from your AWS Lambda functions. It ships as a Lambda Layer and runs as a sidecar process alongside your function for Python, Node.js, and Java runtimes—no code changes, no SDK imports, no wrapper functions. Telemetry is emitted in pure OpenTelemetry format and follows OTel semantic conventions, so Lambda spans correlate naturally with the rest of your stack in Dash0.

Dash0 trace showing a Lambda timeout with synthetic span capturing duration and error status

Key Capabilities

  • Auto-instrumentation: No code changes needed to enable tracing for Python, Node.js, and Java.
  • Lambda context on every trace: Invocation ID, event source, cold start duration, batch record counts, and trigger ARNs for SQS, DynamoDB Streams, Kinesis, SNS, and EventBridge.
  • Synthetic spans for timeouts and out-of-memory errors: Failures that standard OpenTelemetry can't capture because the function is killed before it can emit a trace.
  • Log correlation: Automatic trace correlation through faas.invocation_id.
  • Invocation metrics: Duration, cold start, billed duration, and memory used, generated per invocation.
  • Secret masking: Configurable masking rules for sensitive values in payloads and HTTP bodies.
  • Manual instrumentation path: For functions that already use the OpenTelemetry SDK.
  • Serverless Framework plugin: The serverless-dash0 plugin automatically configures the Dash0 layer for functions marked with dash0-traced: true.

Lambda event payload captured in Dash0 showing the raw event and return value

How It Works

The extension ships as a Lambda Layer that AWS mounts into your function's execution environment at /opt. It runs as a sidecar process with access to Lambda lifecycle events:

  • Instruments your code at startup, before your handler runs.
  • Captures lifecycle events your handler never sees, like timeout and out-of-memory terminations.
  • Collects logs and forwards all telemetry to Dash0 via OTLP.

Because telemetry follows OpenTelemetry semantic conventions, it is portable. If you stop using Dash0, you can redirect the OTLP endpoint without re-instrumenting.

Supported Runtimes

Python, Node.js, and Java, on both x86_64 and arm64 (Graviton) architectures. All non-deprecated versions are supported. See the AWS page for current version support.

Next Steps