We’ve integrated Dynatrace with our Java-based AWS Lambda using the OneAgent ARN-based approach, following the: Trace Python, Node.js, and Java Lambda functions — Dynatrace Docs (Serverless Framework)
The setup seems successful — the Lambda service is detected and visible in Dynatrace under Services. However, we noticed that all transactions are shown as “invoke” instead of the actual endpoint or function names.
Setup details:
Runtime: Java 17
Integration Type: Dynatrace OneAgent ARN (Lambda Layer)
Service visibility: Visible in Dynatrace
Issue: Transactions show up as invoke rather than specific method or endpoint names
Expected: Endpoint-level visibility (e.g. /v1/customers)
Is there any configuration or annotation required in Java Lambdas to enable method-level or endpoint-level detection?
Does the OneAgent ARN integration for Java have any known limitations for naming or trace detection?
- Any sample Java Lambda project integrated with Dynatrace (showing proper endpoint names) would be really helpful.
Thanks in advance for any pointers or best practices!
Featured Posts
