Troubleshoot integration
To troubleshoot issues regarding Dynatrace AWS Lambda extension integration, start with the logs and error messages.
Logs
To get extensive log output on Lambda, add the variables below.
-
For Node.js
1DT_LOGGING_DESTINATION: stdout2DT_LOGGING_NODEJS_FLAGS: Exporter=true,LambdaSensor=true -
For Python
1DT_LOGGING_DESTINATION: stdout2DT_LOGGING_PYTHON_FLAGS: dynatrace=True -
For Java
1DT_LOGGING_DESTINATION: stdout2DT_LOGGING_JAVA_FLAGS: log-Transformer=true,log-OpenTelemetryUtils=true,log-AsyncClassRetransformer=true,log-ClassValue=truelogOpenTelemetryUtils=trueis required foruse-inmemory-exporter(for debugging span-related problems).
Error messages
-
WARNING […] Unexpectedly got HTTP response with Content-Length (...)
This error message is displayed if you don't have port 9999 enabled for your ActiveGate. Go to AWS PrivateLink and VPC endpoints and set up a VPC that allows outbound communication on port 9999 to the ActiveGate endpoint.
OpenTelemetry interoperability
Python
OneAgent will not enable OpenTelemetry interoperability when it detects that the installed OpenTelemetry API version is incompatible. In this case, a line similar to the following is logged:
1[Dynatrace] 2022-07-27 08:55:01.852 UTC [9-dfaf4836] INFO [dynatrace.inject.agent] opentelemetry-api version (1.10.0) is not compatible with Dynatrace SDK (1.9.1).
It is possible to override the compatibility check via configuration. For instance, when you configure OneAgent using the environment variables, add:
DT_OPEN_TELEMETRY_OVERRIDE_MAX_API_VERSION=1.11.1
to allow OpenTelemetry APIs up to version 1.11.1.
Overriding the version compatibility check might result in runtime errors and should be used with caution. You should verify if these errors still occur if an officially supported version of the OpenTelemetry API is used or when temporarily disabling the OpenTelemetry interoperability. If this resolves the problem, please use the older OpenTelemetry API until the newer version is officially supported.