Open danielbdias opened 3 months ago
Pinging code owners:
exporter/datadog: @mx-psi @dineshg13 @liustanley @songy23 @mackjmr
See Adding Labels via Comments if you do not have permissions to add labels yourself.
And folks, can I help on this building a PR? Since I am a Go lang dev too, and I have a test bed to validate this scenario here I want to play a little bit with this issue and contribute to the collector.
/label receiver/datadog -exporter/datadog
Pinging code owners for receiver/datadog: @boostchicken @gouthamve @jpkrohling @MovieStoreGuy. See Adding Labels via Comments if you do not have permissions to add labels yourself.
Assigned the issue to you @danielbdias
Giving a heads up on this issue, I was able to fork it and start building this change.
My work in progress is here: https://github.com/danielbdias/opentelemetry-collector-contrib/tree/add/128-bit-traceid-support-for-datadog-receiver
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Component(s)
receiver/datadog
Describe the issue you're reporting
Hi folks!
During the writing of one article for OTel Blog (https://github.com/open-telemetry/opentelemetry.io/pull/4334) we noticed that
datadog
receiver does not have support for 128-bit trace ids, as described on this CNCF Slack iteration: https://cloud-native.slack.com/archives/C02UN96HZH6/p1714508550552239?thread_ts=1713805772.172779&cid=C02UN96HZH6Can we add an option on this receiver to give support for 128-bit trace ids?