Correlate Sentry errors with OTel traces#1320
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | 086bfa5 | Jul 04 2026, 09:56 AM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | 086bfa5 | Commit Preview URL Branch Preview URL |
Jul 04 2026, 09:55 AM |
Contributor
Cloudflare previewTorn down — the PR is closed. |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
@executor-js/codemode-core
@executor-js/runtime-quickjs
executor
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Sentry error events and the OTel traces exported to Axiom carried unrelated trace ids: Sentry mints its own trace context while the app owns a separate WebTracerProvider, so going from an error event to its request trace (or back) required manual timestamp and attribute joins during incident debugging.
Change
Minimal bidirectional tag join, no trace-context unification:
otel_trace_idandotel_span_idtags from the active OTel span (beforeSendfor auto-captured errors, plus an Effect-aware capture helper for explicit captures).sentry.event_idattribute for the reverse lookup.Sentry.captureExceptioncall sites migrated to the shared helper so they all carry the tags.Full unification (Sentry adopting the OTel trace id as its own) was rejected: the app deliberately opts out of Sentry OTel mode and owns its tracer provider; Sentry Cloudflare OTel mode replaces the global provider and documents no support for custom context handling.
Verification
SENTRY_OTEL_VERIFY=truein the e2e stack) asserting the captured event id, trace id, and span id match between the Sentry payload and the exported span.