Disable server part of netty integration
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- backend, observability-sre
Research direction
The issue names the Netty integration and the Datadog Java compatibility documentation, but no source file or test. Start by tracing the Netty server/client configuration for dd-java-agent 1.52.0 alongside Ktor 3.2.3 and OTel Ktor 2.16.0-alpha; done means server traces can be disabled while client instrumentation remains enabled, with behavior documented and tested.
Written by the indexing model from the issue text.
Description
Library Name
No response
Library Version(s)
No response
Describe the feature you'd like
Hi, due to how the dd-java-agent works with Ktor 3, I decided to try using the io.opentelemetry.instrumentation:opentelemetry-ktor-3.0 library directly and realized that the library tends to better propagate the OTel context. I now would like to disable the netty.request traces that are automatically created, but based on https://docs.datadoghq.com/tracing/trace_collection/compatibility/java, disabling the netty integration disables both the server and the client instrumentation, which is not my intention. Is there any way to selectively disable only the server part of Netty?
Is your feature request related to a problem?
No response
Describe alternatives you've considered
No response
Additional context
Libraries and their version:
- ktor-bom: 3.2.3
- dd-java-agent: 1.52.0
- opentelemetry-bom: 1.52.0
- opentelemetry-ktor-3.0: 2.16.0-alpha
- Dominant language
- Java
- Stars
- 737
- Forks
- 361
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 173
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.
More from DataDog/dd-trace-java
-
type: feature request
Difficulty 1/5 1-3 hours Newbie friendliness 70/100
DataDog/dd-trace-java#10245 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
DataDog/dd-trace-java#12608 ·
-
type: bug report
Difficulty 4/5 3-5 days Newbie friendliness 35/100
DataDog/dd-trace-java#12597 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
DataDog/dd-trace-java#12540 · 3 comments · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
DataDog/dd-trace-java#12480 ·
All issues in DataDog/dd-trace-java
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
enhancement Tools
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
apache/rocketmq-dashboard#5008 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
DETECT_PARAMETER_NAMES=false silently disables @ConstructorProperties-based Creator detection too Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FasterXML/jackson-databind#6229 ·