Repository navigation
docs(js): Add OpenTelemetry JS v3 example to custom OpenTelemetry setup - #20142
sentry-junior[bot] wants to merge 4 commits into
Conversation
Co-Authored-By: Andrei Borza <andrei.borza@sentry.io>
Co-Authored-By: Andrei Borza <andrei.borza@sentry.io>
Co-Authored-By: Andrei Borza <andrei.borza@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
|
The plan checks loads of the custom OpenTelemetry setup page, client errors on that path, and code-tab errors. An issue escalates when those errors appear or when loads on that path fall to zero. Services: Mention PlanWhat changedJavaScript server custom OpenTelemetry setup pages now show an OpenTelemetry JS v3 example tab beside the v2 tab. The v3 tab starts NodeSDK and imports BatchSpanProcessor from RiskA broken tab group can crash the code-tab client on this page. Readers then lose both the new v3 snippet and the old v2 snippet. If the page fails to generate, those guide URLs return not found. Wrong tab content can send readers to an API that does not match their OpenTelemetry JS version. Intended effectThis change is a documentation content edit. No metric records that the v3 tab is visible. The executor cannot set intended_effect to confirmed from telemetry. absent would mean the v3 tab is missing while the page still loads. Telemetry cannot show that case. Regression watchClient traces use a 30 percent sample rate. Error events are not sampled the same way. A 24 hour sampled count of 0 is a real drop. A miss of one or two sampled loads may be sample noise.
If the error rate rises, check client error titles for CodeTabs or a failed MDX render on these URLs. Not observableNo signal shows which tab is selected or whether the v3 snippet text is present. No http.server spans matched this path, so server status codes on these URLs are not available. |
Co-Authored-By: Andrei Borza <andrei.borza@sentry.io>
DESCRIBE YOUR PR
The "Use Your Own OpenTelemetry Pipeline" page only showed an OpenTelemetry JS v2 setup. OpenTelemetry JS v3 replaces
@opentelemetry/sdk-trace-baseand@opentelemetry/sdk-trace-nodewith@opentelemetry/sdk-trace, dropsNodeTracerProvider, and changesBatchSpanProcessorto take an options object, so the v2 snippet doesn't work after upgrading.This adds a v3 tab (
NodeSDK+@opentelemetry/sdk-trace) next to the existing v2 example and notes the Node.js 22.15+ requirement. The v3 setup mirrors the e2e app added in getsentry/sentry-javascript#25630.IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST
via Andrei Borza.
--
View Junior Session [Sentry]