From 391365a42d2af69e1a03272e730fdd3120be8850 Mon Sep 17 00:00:00 2001 From: Ayan Khan Date: Thu, 16 May 2024 13:31:14 -0400 Subject: [PATCH] set an explicit version range for the @opentelemetry/api --- README.md | 9 ++++++++- package.json | 2 +- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 021604873f2..349b0a51478 100644 --- a/README.md +++ b/README.md @@ -108,4 +108,11 @@ If you would like to trace your bundled application then please read this page o ## Security Vulnerabilities -Please refer to the [SECURITY.md](https://github.com/DataDog/dd-trace-js/blob/master/SECURITY.md) document if you have found a security issue. \ No newline at end of file +Please refer to the [SECURITY.md](https://github.com/DataDog/dd-trace-js/blob/master/SECURITY.md) document if you have found a security issue. + +## Datadog With OpenTelemetery + +Please refer to the [Node.js Custom Instrumentation using OpenTelemetry API](https://docs.datadoghq.com/tracing/trace_collection/custom_instrumentation/nodejs/otel/) document. It includes information on how to use the OpenTelemetry API with dd-trace-js + +Note that our internal implementation of the OpenTelemetry API is currently set within the version range `>=1.0.0 <1.9.0`. This range will be updated at a regular cadence therefore, we recommend updating your tracer to the latest release to ensure up to date support. + diff --git a/package.json b/package.json index 33a8a603659..39ff5019f94 100644 --- a/package.json +++ b/package.json @@ -76,7 +76,7 @@ "@datadog/native-metrics": "^2.0.0", "@datadog/pprof": "5.3.0", "@datadog/sketches-js": "^2.1.0", - "@opentelemetry/api": "^1.0.0", + "@opentelemetry/api": ">=1.0.0 <1.9.0", "@opentelemetry/core": "^1.14.0", "crypto-randomuuid": "^1.0.0", "dc-polyfill": "^0.1.4",