Closed povilasv closed 1 week ago
receiver/datadog
Looks like we are missing container id in DD receiver, and this makes some screens in DD don't work (when received and exported thru collector)
I've got details of some request:
Sending request: PUT v0.5/traces {'Datadog-Meta-Lang': 'python', 'Datadog-Meta-Lang-Version': '3.10.14', 'Datadog-Meta-Lang-Interpreter': 'CPython', 'Datadog-Meta-Tracer-Version': '2.7.2', 'Datadog-Client-Computed-Top-Level': 'yes', 'Datadog-Container-Id': '7d0f62eb396bd016230ebc53d525bd6bc9ce734894fcf70b39f268b62001a79d', 'Datadog-Entity-ID': 'cid-7d0f62eb396bd016230ebc53d525bd6bc9ce734894fcf70b39f268b62001a79d', 'Content-Type': 'application/msgpack', 'X-Datadog-Trace-Count': '1'}
Looks like Datadog-Container-Id is the header. I've looked thru exporter code and it should pick up container id from semconv, so in theory should work.
Datadog-Container-Id
No response
Pinging code owners:
receiver/datadog: @boostchicken @gouthamve @jpkrohling @MovieStoreGuy
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Component(s)
receiver/datadog
Is your feature request related to a problem? Please describe.
Looks like we are missing container id in DD receiver, and this makes some screens in DD don't work (when received and exported thru collector)
Describe the solution you'd like
I've got details of some request:
Looks like
Datadog-Container-Id
is the header. I've looked thru exporter code and it should pick up container id from semconv, so in theory should work.Describe alternatives you've considered
No response
Additional context
No response