-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WARN datadog.trace.agent.core.propagation.ptags.W3CPTagsCodec
: Invalid datadog tags header value
#6725
Comments
To help us investigate the issue, can you tell me more about the upstream service(s) talking to the application that raise this warn log. The decision marker tag ( |
I get the same thing using scala, cats-effect & redis |
What exactly are you looking for? The service is a fairly simple kotlin springboot API. No database. Talks to kafka and some other APIs. Most of the time, there's a corresponding API request that comes in, we process, write to kafka, then the error shows up. But it doesn't happen every time. And I don't know if that pattern is always consistent. Here's the relevant datadog configuration (with some details redacted): $ env | grep "DD_"
DD_DBM_PROPAGATION_MODE=full
DD_JMXFETCH_KAFKA_ENABLED=true
DD_JMXFETCH_ENABLED=true
DD_PROFILING_ENABLED=false
DD_LOGS_INJECTION=true
DD_ENV=dev
DD_VERSION=1.0.18
DD_RUNTIME_METRICS_ENABLED=true
DD_SERVICE_MAPPING=mysql:mysql-<service>
DD_DATA_STREAMS_ENABLED=true
DD_AGENT_HOST=<10.*.*.*>
DD_SERVICE=<service>
DD_TRACE_HEALTH_METRICS_STATSD_PORT=8125
DD_INTEGRATION_JDBC_DATASOURCE_ENABLED=true
DD_KAFKA_LEGACY_TRACING_ENABLED=false |
I am looking for information about the service that calls your SpringBoot/Kotlin application through its API (the upstream service): flowchart LR
A[Upstream service] --> |API| B[SpringBoot/Kotlin]
style A stroke:#f66,stroke-width:2px,stroke-dasharray: 5 5
B --> C[Kafka]
B --> |API| D[Downstream service]
It looks to be the one sending API requests with invalid headers to your SpringBoot app. |
We have been experiencing the following WARN logs coming out of
dd-java-agent
that wraps our springboot service utilizingdd-trace-java
:Just upgraded both
dd-trace-java
anddd-java-agent
to1.30.0
and we're still seeing it. I think this is similar to #5930, but maybe not exactly given the header value differences. Thought I'd submit it anyway to see if anyone has a fix.The text was updated successfully, but these errors were encountered: