Skip to content

Commit bdbbfa2

Browse files
authored
fix: Update OTEL js custom instructions snippet (#10519)
* fix: Update OTEL js custom instructions snippet Make sure we only have a single provider * Update docs/platforms/javascript/common/tracing/instrumentation/opentelemetry.mdx
1 parent 2dd53bb commit bdbbfa2

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

docs/platforms/javascript/common/tracing/instrumentation/opentelemetry.mdx

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -72,22 +72,24 @@ Sentry.init({
7272
tracesSampleRate: 1.0,
7373
});
7474

75-
// This e.g. sets up @opentelemetry/sdk-trace-node
76-
const provider = manuallySetUpOpenTelemetry();
75+
const sentryClient = Sentry.getClient();
76+
77+
// Note: This could be BasicTracerProvider or any other provider depending on
78+
// how you are using the OpenTelemetry SDK
79+
const provider = new NodeTracerProvider({
80+
// We need our sampler to ensure the correct subset of traces is sent to Sentry
81+
sampler: sentryClient ? new SentrySampler(sentryClient) : undefined,
82+
});
7783

7884
// We need a custom span processor
7985
provider.addSpanProcessor(new SentrySpanProcessor());
86+
8087
// We need a custom propagator and context manager
8188
provider.register({
8289
propagator: new SentryPropagator(),
8390
contextManager: new Sentry.SentryContextManager(),
8491
});
8592

86-
// We need our sampler to ensure the correct subset of traces is sent to Sentry
87-
const provider = new BasicTracerProvider({
88-
sampler: new SentrySampler(Sentry.getClient()),
89-
});
90-
9193
// Validate that the setup is correct
9294
Sentry.validateOpenTelemetrySetup();
9395
```

0 commit comments

Comments
 (0)