Troubleshoot monitoring issues for AWS Lambda
To troubleshoot issues regarding OneAgent-Lambda integration, start with the logs and error messages.
Logs
To get extensive log output on Lambda, add the variables below.
- For Node.js
DT_LOGGING_DESTINATION: stdout
DT_LOGGING_NODEJS_FLAGS: Exporter=true,LambdaSensor=true
- For Python
DT_LOGGING_DESTINATION: stdout
DT_LOGGING_PYTHON_FLAGS: dynatrace=True
- For Java
DT_LOGGING_DESTINATION: stdout
DT_LOGGING_JAVA_FLAGS: log-Transformer=true,log-EmbeddedJarClassLoader=true,log-OpenTelemetryUtils=true,log-AsyncClassRetransformer=true,log-ClassValue=true
Note: logOpenTelemetryUtils=true
is required for use-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.