Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated to make it work with tracing without performance. #100

Merged
merged 4 commits into from
Jun 20, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update text/0071-continue-trace-over-process-boundaries.md
Co-authored-by: Michi Hoffmann <[email protected]>
  • Loading branch information
antonpirker and cleptric authored Jun 6, 2023
commit 6ae3eb3590a6a69ff7ce0e7f48f0975bf0978bc6
2 changes: 1 addition & 1 deletion text/0071-continue-trace-over-process-boundaries.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ If `SENTRY_TRACING_USE_ENVIRONMENT` is set to `false` (or rather `false|False|FA
- `SENTRY_TRACING_SENTRY_TRACE` (similar to `sentry-trace` HTTP header)

The environment variables contain the same strings that the respecitve HTTP headers would contain.
The SDK parses the string values from the environment variables and stores the information on the scope.
The SDK parses the string values from the environment variables and stores the information in the propagation context on the scope.

To successfully attach a transaction to an existing trace at least `SENTRY_TRACING_SENTRY_TRACE` must have data.

Expand Down