docs: add changelog entry for infrastructure scaling improvements#2516
docs: add changelog entry for infrastructure scaling improvements#2516maxdeichmann wants to merge 28 commits intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ellipsis-dev
bot
changed the title
📦 Next.js Bundle Analysis for langfuse-docsThis analysis was generated by the Next.js Bundle Analysis action. 🤖 New Page AddedThe following page was added to the bundle from the code in this PR:
|
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Langfuse-Trace: https://cloud.langfuse.com/trace/bd3368b5b43c7ba9b2d4aaf19e443a94
This reverts commit 456b572. Langfuse-Trace: https://cloud.langfuse.com/trace/862381a48a9d71cf43f5c4ab8baf8246
|
|
||
| The data model now centers on [observations](/docs/observability/data-model#observations) as the primary concept. | ||
|
|
||
| Context attributes (`user_id`, `session_id`, `metadata`) set at the trace level now propagate automatically to all child spans. This eliminates the need to repeatedly update trace metadata or patch outputs across observations. |
There was a problem hiding this comment.
Is this something we actually want to promise here? Because with SDK upgrades, this relies on users using the propagate attributes method correctly. Currently, this is just for transition.
If we want to keep this section brief, we could state that this happens automatically for "old" SDKs, but causes an ingestion delay, or happens client side with instant data availability.
| - **Python SDK**: v4 ([migration guide](/docs/observability/sdk/upgrade-path/python-v3-to-v4)) | ||
| - **JS/TS SDK**: v5 ([migration guide](/docs/observability/sdk/upgrade-path/js-v4-to-v5)) | ||
|
|
||
| The key change: `update_current_trace()` / `updateActiveTrace()` is replaced by `propagate_attributes()`, which automatically flows attributes like `user_id`, `session_id`, `metadata`, and `tags` to all child observations. |
There was a problem hiding this comment.
| The key change: `update_current_trace()` / `updateActiveTrace()` is replaced by `propagate_attributes()`, which automatically flows attributes like `user_id`, `session_id`, `metadata`, and `tags` to all child observations. | |
| The key change: `update_current_trace()` / `updateActiveTrace()` is replaced by `propagate_attributes()`, which automatically pushes attributes like `user_id`, `session_id`, `metadata`, and `tags` to all child observations. |
| - JS/TS debug mode: set `LANGFUSE_DEBUG="true"` (or `LANGFUSE_LOG_LEVEL="DEBUG"`). | ||
| - See [SDK advanced features](/docs/observability/sdk/advanced-features) and [OpenTelemetry troubleshooting for unwanted spans](/faq/all/existing-otel-setup#unwanted-spans-in-langfuse). | ||
|
|
||
| ### `updateActiveTrace()` decomposed into 3 functions |
There was a problem hiding this comment.
IMO the 3 functions heading here is misleading as this section only covers propagateAttributes. Either this needs an introduction sentence that explains why it's a three-way split, or another heading.
| - Python debug mode: use `Langfuse(debug=True)` or set `LANGFUSE_DEBUG="True"`. | ||
| - See [SDK advanced features](/docs/observability/sdk/advanced-features) and [OpenTelemetry troubleshooting for unwanted spans](/faq/all/existing-otel-setup#unwanted-spans-in-langfuse). | ||
|
|
||
| ### `update_current_trace()` decomposed into 3 methods |
| @@ -0,0 +1,166 @@ | |||
| # Langfuse JS/TS SDK v5 — Breaking Changes | |||
There was a problem hiding this comment.
Are these supposed to live at the root level?
Contributes to LFE-8708
| ## A note for self-hosted users | ||
|
|
||
| <Callout type="warning"> | ||
| The changes described above are currently available on **Langfuse Cloud only**. | ||
| We do not have a timeline yet for self-hosted availability. | ||
| </Callout> | ||
|
|
||
| Our team is actively working on a path for self-hosters to adopt the new observation-centric data model. | ||
| This is a core priority for our team over the coming weeks. | ||
| Unfortunately, we cannot provide a timeline for a corresponding release, yet. | ||
|
|
||
| [//]: # (TODO: Add link to discussion) | ||
| We will share updates in the [changelog](/changelog) and on [GitHub Discussions]() | ||
| as they become available. |
There was a problem hiding this comment.
@maxdeichmann I would propose that we proactively open a new GitHub discussion and link it here. Otherwise, I tried to keep it brief and on the point without making strong timeline promises.
Please review and adjust as you see fit.
6 participants
Important
Added a new changelog entry documenting infrastructure scaling improvements including an observation-centric data model, UI performance enhancements, new v2 API endpoints, and supporting images.
2026-02-10-simplify-for-scale.mdxdocumenting major infrastructure changes:v4-banner.png,data-model.png,v4-perf-comparison.png)This description was created by
for 49c81a6. You can customize this summary. It will automatically update as commits are pushed.