From ffe00a777674ef25b2a306a0fa69d999e23d9dad Mon Sep 17 00:00:00 2001 From: Daniel Visca Date: Tue, 25 Aug 2026 09:20:14 -0700 Subject: [PATCH] chore: add changeset for capture_trace_context PR #894 merged without a changeset, so Sampo has nothing pending and the option won't be published. Adds the missing minor changeset for the already-merged capture_trace_context option. Generated-By: PostHog Desktop Task-Id: 44c7be3e-4938-4f9a-bb80-89fd9d74db6d --- .sampo/changesets/eager-wayfarer-ahti.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 .sampo/changesets/eager-wayfarer-ahti.md diff --git a/.sampo/changesets/eager-wayfarer-ahti.md b/.sampo/changesets/eager-wayfarer-ahti.md new file mode 100644 index 000000000..acb75552b --- /dev/null +++ b/.sampo/changesets/eager-wayfarer-ahti.md @@ -0,0 +1,5 @@ +--- +pypi/posthog: minor +--- + +Add an opt-in `capture_trace_context` client option. When enabled, and a valid OpenTelemetry span is active at capture time, its trace and span IDs are attached to events captured with `capture()` and `capture_ai()` as `$trace_id` and `$span_id`, so they can be correlated with backend traces. Disabled by default, and explicit `$trace_id`/`$span_id` properties take precedence.