Open spencerwilson opened 3 years ago
Workaround: Rather than sending trace data from my Node.js process directly to Datadog, I'm probably gonna export it via @opentelemetry/exporter-collector-grpc to an OpenTelemetry Collector configured to run the Datadog exporter. I also notice that this'll happily put us in compliance with the guidance added in https://github.com/DataDog/documentation/pull/9824:
Datadog recommends you use the OpenTelemetry Collector Datadog exporter in conjunction with OpenTelemetry tracing clients [, with the language-specific exporters as a secondary option]
P.S. Thanks @ericmustin for your effort to bring OTel support to Datadog! As a customer, I appreciate it.
@spencerwilson 👋 hope all is well. apologies for the state of affairs of this repo, it is indeed a bit out of date with latest node and also just in general with latest opentelemetry-js. For context, we're working on adding OTLP Support directly to the datadog-agent, which would preclude the need for these helper libs in every language. In the meantime the suggested setup is to use the opentelemetry-collector (contrib flavor) and the datadogexporter.
Describe the bug On 7682aab aka v0.2.0,
npm install
on Node.js 16+ (the "Current" major version; will become "Active" LTS on 2021-10-26) fails during installation of the transitive dependencydd-trace
:To Reproduce Steps to reproduce the behavior:
npm install
using Node.js 16.x on any platformExpected behavior Installs without error
Additional context
I confirmed that the package can successfully be installed after applying
but under that patch, 35 of the 45 non-
skip
ed tests fail:For more info on the
dd-trace
bug, see https://github.com/DataDog/dd-trace-js/issues/1388.