For information about differences between classic services and other services, see Migrate from AWS classic (formerly "built-in") services to cloud services.
AWS Lambda lets you run code without provisioning or managing servers. This deployment model is sometimes referred to as "serverless" or "Function as a Service" (FaaS).
Trace Python, Node.js, and Java Lambda functions
Trace .NET Lambda functions AWS Lambda log collection
Monitor AWS Lambda (built-in) for metrics, properties and tags from AWS
OpenTelemetry interoperability
AWS Lambda logs in context of traces
For AWS Lambda, monitoring consumption is based on Davis data units. See Serverless monitoring for details.
Dynatrace support for Lambda is aligned with the AWS Lambda runtimes lifecycle, which consists of two Deprecation Phases. To learn more about the Dynatrace support level for each runtime, see the table below. Once a runtime reaches Deprecation Phase 2, Dynatrace will no longer provide technical support due to the technical limitations that are in effect for functions on such runtimes.
If you have Lambda functions on a runtime that is entering any Deprecation Phase, we recommend that you prepare to migrate to a supported runtime as soon as possible.
dotnetcore3.1dotnet6dotnet8java8.al2java11java17java21nodejs10.xnodejs12.xnodejs14.xnodejs16.xnodejs18.xnodejs20.xpython3.8python3.9python3.10python3.11python3.12Only .NET 7 functions deployed as container images are supported. AWS has not released a managed runtime for .NET 7.