Skip to main content
AWS Lambda emits function logs (your application output), platform logs (cold starts, timeouts, out-of-memory events), and — when instrumented — distributed traces. The right ingestion path depends on your runtime and whether you also want traces. ADOT Lambda Layer — sends logs and traces directly to Bronto over OTLP on OTel-supported runtimes (Node.js, Python, Java, .NET, and Go). It bypasses CloudWatch entirely, avoiding CloudWatch ingestion fees, and uses the same service.name / service.namespace routing as your other OTel workloads (see Data Organization).

​
Alternatives

  • CloudWatch Log Forwarder — captures Lambda’s automatic stdout / stderr and works with runtimes the ADOT layer doesn’t support (Ruby, custom runtimes).
See Ingesting AWS Data into Bronto for the full service-to-method mapping.

​
References