docs(vercel): nested executions within parent trace

[hassiebp]

Important

Adds documentation for grouping multiple executions under a single trace and handling short-lived environments in Vercel AI SDK using Langfuse.

• Documentation:
  • Adds section on grouping multiple executions in one trace using Langfuse in vercel-ai-sdk.mdx.
  • Provides TypeScript example for grouping executions with Langfuse.trace() and generateText().
  • Adds image illustrating nested trace hierarchy in Langfuse UI.
• Short-lived Environments:
  • Adds instructions for forcing export and flushing of spans in short-lived environments using forceFlush method on LangfuseExporter.

^{This description was created by for 90998c1. It will automatically update as commits are pushed.}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
langfuse-docs	✅ Ready (Inspect)	Visit Preview	Nov 25, 2024 3:11pm

[github-actions]

📦 Next.js Bundle Analysis for langfuse-docs

This analysis was generated by the Next.js Bundle Analysis action. 🤖

One Page Changed Size

The following page changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load	% of Budget (350 KB)
/docs/integrations/vercel-ai-sdk	32.41 KB	362.51 KB	103.57% (🟡 +0.29%)

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.