Dynatrace provides enhancements to OpenTelemetry for AWS Lambda such as exporters, additional instrumentation, and helper libraries to simplify the monitoring of AWS Lambda.
For a list of language-specific packages that you can use in combination with the native OpenTelemetry SDKs and APIs or AWS Distribution for OpenTelemetry, see Trace .NET Lambda functions.
Select a monitoring solution and configuration method
Specify a Dynatrace API endpoint
Apply the configuration to your AWS Lambda function
Instrument the function code
Configuration options regarding Lambda layers don't apply here.
In Dynatrace Hub, select AWS Lambda.
Select Set up.
On the Enable Monitoring for AWS Lambda Functions page, set Select a runtime to .NET.
This automatically sets Monitoring solution to AWS Lambda OpenTelemetry package.
Set Select a configuration method to your preferred configuration method. Make sure you set all properties for the chosen configuration method.
If you don't want to use the default public Dynatrace endpoint, specify a custom Dynatrace API endpoint where you want to receive monitoring data.
To reduce network latency, you typically deploy a Dynatrace ActiveGate close to (in the same region as) the AWS Lambda function that you want to monitor.
To apply the configuration, select one of the options below, depending on your configuration method.
Copy the JSON snippet into a file named dtconfig.json
located in the root folder of your AWS Lambda Functions deployment.
On Enable Monitoring for AWS Lambda Functions, under Use the following values to define environment variables for your AWS Lambda function, there's a snippet with all required environment variables. Be sure to add these environment variables and their values to your Lambda function configuration. For details, see Configuring environment variables.
Adding the required API calls to monitor function invocations via OpenTelemetry is specific to languages and their respective OpenTelemetry distribution.
To get detailed instructions for different languages supported by Dynatrace, see Trace .NET Lambda functions.
The Dynatrace instrumentation doesn't capture the IP addresses of outgoing HTTP requests. If the called service isn't monitored with Dynatrace, this results in unmonitored hosts.