From b2082d32d50c88ccdcc11ecd246f6b86851a57c2 Mon Sep 17 00:00:00 2001 From: Charly Gomez Date: Mon, 26 Aug 2024 11:27:28 +0200 Subject: [PATCH] docs: Update TracerProvider docs (#11131) --- .../common/opentelemetry/using-opentelemetry-apis.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/javascript/common/opentelemetry/using-opentelemetry-apis.mdx b/docs/platforms/javascript/common/opentelemetry/using-opentelemetry-apis.mdx index 18272673172e0..46a3d21133242 100644 --- a/docs/platforms/javascript/common/opentelemetry/using-opentelemetry-apis.mdx +++ b/docs/platforms/javascript/common/opentelemetry/using-opentelemetry-apis.mdx @@ -68,7 +68,7 @@ You can also use any other tracer. All OpenTelemetry spans will be picked up by ## Modifying the default OpenTelemetry TracerProvider -You can access the tracer provider set up by Sentry when using Sentry's default OpenTelemetry instrumentation. This makes it easy to, for example, add additional span processors if you want to send span data to another backend or similar. +You can access the tracer provider set up by Sentry when using Sentry's default OpenTelemetry instrumentation. This enables you to easily add additional span processors, allowing you to export tracing data to various OTEL collectors or other backends. ```javascript const Sentry = require("@sentry/node");