PostHog Product updatestable Released Nov 04, 2026
Impact Score: 7/10

PostHog: Trace context across server SDKs

Source available — automated, not human-reviewed

Component: posthog · Channel: stable. Automated analysis, not a compatibility certification. How this works.

Analysis updated: 2026-11-04.

Automated impact estimate — compatibility not verified
📄 .MD
⚡ Executive Summary (TL;DR)

PostHog has updated its server SDKs to propagate trace and request context across errors and application spans. This enhancement allows developers to effortlessly trace application failures back to their originating requests across multiple languages including Java, .NET, Go, and Ruby.

Who Does This Impact? (Role-Based Analysis)

💻 Software Engineers & Devs

Engineers using PostHog server SDKs can now automatically attach trace IDs and request context to exceptions and application spans to simplify debugging.

📊 Product & Engineering Leads

Improved error tracking and distributed tracing capabilities accelerate root-cause analysis and enhance application reliability.

⚙️ DevOps & Security

No direct CI/CD or infrastructure deployment impacts are introduced by this tracing update.

✨ New Features & Capabilities (8)

  • Java: added active trace IDs to exceptions and request context to application spans
  • .NET: added trace context to captured exceptions and request context to application spans
  • Elixir: added trace context to exceptions and optional request context to application spans
  • Go: added opt-in trace context to exceptions and request context to application spans
  • Ruby and Rails: added trace context to exceptions and correlated request and child spans
  • PHP: added an optional application-span context processor
  • Rust: added request context, Tower middleware, and a Reqwest client that propagates it
  • Node.js: added request context to OpenTelemetry application spans