Blob storage, PostHog, and Mixpanel exports default to enriched observations for new Cloud projects
Niklas Semmler, PhDNew Langfuse Cloud projects use enriched observations for blob storage, PostHog, and Mixpanel exports. The legacy traces/observations sources stay available on existing projects and self-hosted deployments.
Blob storage, PostHog, and Mixpanel integrations on Cloud projects created on or after 2026-05-20 use the Enriched observations (recommended) source. The Traces and observations (legacy) and Traces and observations (legacy) and enriched observations sources are hidden from the UI for these projects. For blob storage, the REST API also rejects legacy values for post-cutoff projects with 400 BAD_REQUEST.
Nothing changes for existing Cloud projects or self-hosted deployments: all three sources remain available and the legacy sources are fully supported. Existing Cloud projects can switch to Enriched observations at any time.
Enriched observations are part of the Langfuse v4 data model, which introduced a single denormalized observation row as the canonical export shape across all integrations.
If a downstream consumer expects the legacy traces/ and observations/ file shapes, see the Export Field Reference for the column map between the two layouts.