fraqtal/agentic-dev
Template
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
f77e6ea881a8a2a1c63a0aee897e110616e9fae1
agentic-dev/docs/library-decisions/2026-05-14-@sentry/opentelemetry.md
Danijel Martinek f77e6ea881 chore(template): clean-slate template snapshot from bb4a0c7 
Curated, product-agnostic snapshot of the post-story-04 tree: demo
content deleted, auth-only reference feature, web-next shell, all gates
green. Product-specific docs, ADRs 027-029, PRDs/epics/archive, editor
library traces, and product naming are curated out; generic template
repairs (coverage provider devDeps, root test:coverage script, live
lint fixes, root-only release-please) are kept. See TEMPLATE.md for
provenance, curation list, and usage.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016j8z4VHjedXDTjEDNg7qHK
2026-07-12 20:40:54 +02:00

3.5 KiB
Raw Blame History

package, version, tier, decision, date, deciders, adr, filter-results, verification-commands, accepted-cves
package version tier decision date deciders adr filter-results verification-commands accepted-cves
@sentry/opentelemetry ^10.51.0 core approved 2026-05-14
Danijel Martinek
adr-014
license types maintenance boundary-fit shadow-check eu-residency cve-scan named-consumer socketRisk
MIT native active pass pass ok clean pass clean
npm view @sentry/opentelemetry license
npm view @sentry/opentelemetry version
pnpm audit --audit-level=moderate

Filter: license

npm view @sentry/opentelemetry license returns MIT. MIT is on the allowlist.

Filter: types

@sentry/opentelemetry is authored in TypeScript and ships its own .d.ts declaration files. No separate @types/ package is needed.

Filter: maintenance

Actively maintained by Sentry Inc. as the official bridge between the Sentry SDK and the OpenTelemetry SDK. Versions track the @sentry/* SDK family; the 10.x line is current.

Filter: boundary-fit

ADR-014 designates Sentry as the error-capture backend, and ADR-017 mandates OpenTelemetry as the instrumentation substrate. @sentry/opentelemetry is the bridge that wires Sentry as an OTel exporter — it belongs exclusively in core-shared/instrumentation/sentry/ alongside the adapter pair. Feature packages MUST NOT import it directly (ESLint no-restricted-imports, ADR-014 §6).

Filter: shadow-check

@sentry/opentelemetry is the only OTel-to-Sentry bridge in the workspace. No competing exporter bridge (e.g., manual @opentelemetry/exporter-* wired to Sentry) is present.

Filter: eu-residency

@sentry/opentelemetry is a pure instrumentation adapter with no independent data transmission. All spans and log records it emits are forwarded through the Sentry SDK, which routes to the DSN host (EU-hosted if configured). EU residency is governed by the DSN setting, not this package.

Filter: cve-scan

pnpm audit --audit-level=moderate reports no advisories against @sentry/opentelemetry at the time of this trace.

Filter: named-consumer

packages/core-shared/src/instrumentation/sentry/ is the sole consumer. It registers @sentry/opentelemetry's SentrySpanProcessor and SentryPropagator during OTel SDK initialization so that all OTel spans are also captured as Sentry transactions.

Prompt: replaces

Prior to ADR-017, the workspace had no OTel substrate. @sentry/opentelemetry replaces the need to configure two independent pipelines (a direct Sentry SDK pipeline and a raw OTel SDK pipeline) by letting a single OTel pipeline export to Sentry via the bridge.

Prompt: migration-cost-out

Low. @sentry/opentelemetry is used in one file in core-shared/instrumentation/sentry/. Replacing Sentry as the exporter means swapping this bridge for a different SpanExporter in that single file. The OTel substrate (ADR-017) remains untouched.

Prompt: alternatives-considered

  1. Direct Sentry SDK without OTel bridge — Rejected in ADR-017: coupling feature packages to @sentry/* APIs directly would violate vendor isolation. The OTel-first approach keeps instrumentation portable.
  2. @opentelemetry/exporter-zipkin / Jaeger — Open-source trace backends considered but lack Sentry's session replay, error deduplication, and release tracking. Sentry via bridge offers a superset.

See ADR-014 and ADR-017 for the full decision rationale.