newrelic / newrelic/newrelic-java-agent
Micronaut 4.4.0 + Tomcat results in "Unknown DTs / txn traces"
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 240
- Forks
- 170
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 21
Description
Description
Customer states that after upgrading to Micronaut 4.4.0 they started seeing "Unknown DTs / txn traces" when using Tomcat, however Netty produces the correct information. This is the opposite of what's being seen in #2106
Internal Slack thread
Customer has provided 2 repro apps (Attached) - One with TC (non-working) and one with Netty (works).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running and comparing the attached Tomcat and Netty reproduction apps with Micronaut 4.4.0. Trace how each setup reports DTs and transaction traces, using the working Netty behavior as the comparison point. Done means the Tomcat reproduction reports the correct information instead of "Unknown DTs / txn traces."
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100