Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: explain span filtering for otel #1272

Merged
merged 1 commit into from
Feb 11, 2025
Merged

Conversation

Steffen911
Copy link
Contributor

@Steffen911 Steffen911 commented Feb 11, 2025

Important

Adds documentation on filtering OpenTelemetry spans for Langfuse, including configuration examples and warnings.

  • Documentation:
    • Adds section on filtering spans in get-started.mdx for OpenTelemetry with Langfuse.
    • Provides configuration example using filterprocessor to filter spans with gen_ai.system attribute set to openai.
    • Warns about potential incomplete traces and the necessity of sending root spans.

This description was created by Ellipsis for 38d235e. It will automatically update as commits are pushed.

Copy link

vercel bot commented Feb 11, 2025

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

Name Status Preview Updated (UTC)
langfuse-docs ✅ Ready (Inspect) Visit Preview Feb 11, 2025 10:33am

@dosubot dosubot bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Feb 11, 2025
@Steffen911 Steffen911 enabled auto-merge February 11, 2025 10:27
@dosubot dosubot bot added auto-merge This PR is set to be merged documentation Improvements or additions to documentation labels Feb 11, 2025
Copy link

📦 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/opentelemetry/get-started 38.54 KB 372.34 KB 106.38% (🟡 +0.16%)
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.

@Steffen911 Steffen911 added this pull request to the merge queue Feb 11, 2025
Merged via the queue into main with commit a85dcd6 Feb 11, 2025
8 checks passed
@Steffen911 Steffen911 deleted the steffen/otel-filters branch February 11, 2025 10:38
@dosubot dosubot bot removed the auto-merge This PR is set to be merged label Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation size:M This PR changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant