Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Netty 4.0 integration doesn't seem to work
See original GitHub issueSummary
I’ve followed https://docs.datadoghq.com/tracing/setup/java/, but the Netty 4.0 Client instrumentation doesn’t seem to work with Play 2.5 or even just AHC 2.0 by itself.
Expected result
I expect x-datadog-trace-id, x-datadog-parent-id headers attached to the outbound HTTP request, and a child span named netty.client.request.
I get neither.
Repro
I’ve replicated Netty40ClientTest in a new project: https://github.com/htmldoug/datadog-netty4-failing.
You can repro with sbt run.
Screenshots
Relates to #352. cc: @tylerbenson @realark
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’ve logged that as a new issue, https://github.com/DataDog/dd-trace-java/issues/432. I think it’s more of a play-integration issue than a netty issue. I’m pretty satisfied with the netty part. Thanks!
It was funny, your report came in right as we were investigating it ourselves. We were trying to figure out why the netty instrumentation wasn’t working with Spring Webflux. So we already had a few hours head start . 😉
@htmldoug you can try the jar built by CI: https://7229-89221572-gh.circle-artifacts.com/0/home/circleci/dd-trace-java/libs/dd-java-agent-0.12.0-SNAPSHOT.jar For PR’s, we save it as artifacts on the CI, but when it gets merged to master, there will be a snapshot published to the snapshot repo.