Skip to content

Conversation

@Lotte-Verheyden
Copy link
Contributor

@Lotte-Verheyden Lotte-Verheyden commented Nov 28, 2025

Important

This PR improves observability documentation by restructuring content, enhancing clarity, and updating related pricing and FAQ components.

  • Documentation Restructuring:
    • Renames data-model to Concepts in observability/_meta.tsx.
    • Moves billable units information to administration/billable-units.mdx and updates links in PricingCalculator.tsx, PricingFAQ.tsx, and PricingTable.tsx.
    • Updates observability/overview.mdx and observability/get-started.mdx to provide clearer guidance on tracing setup and core concepts.
  • Content Enhancements:
    • Adds detailed explanations of traces, observations, and sessions in data-model.mdx.
    • Provides step-by-step setup instructions for various SDKs in get-started markdown files.
    • Introduces a new auto-install.mdx for agent-based setup.
  • Pricing and FAQ Updates:
    • Updates pricing-related components to reflect new documentation structure.
    • Enhances FAQ entries to address common user issues with observability setup and cost management.

This description was created by Ellipsis for 44ef670. You can customize this summary. It will automatically update as commits are pushed.

- add the sessions - traces - observations explanation here since it's fundamental
- add context on observability
- link to opentelemetry and explain what it is
- nudge users to best next steps ("how to get the most out of tracing')
- moved billable units to its separate page under Administration/Misc
- updated references to billable units on the pricing page
- added section on how langfuse works in the background
- added intro referring to get started guide
- added diagrams, styled them consistently
- Removed OpenTelemetry explanation from the overview page
- improved docstrings on all 4 integrations
- included both inline setups and instrumentation file approach in both JS/TS options
- added short description on instrumentation
- rewrote capturing data paragraphs
@vercel
Copy link

vercel bot commented Nov 28, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
langfuse-docs Ready Ready Preview Comment Nov 28, 2025 4:03pm

@github-actions
Copy link

github-actions bot commented Nov 28, 2025

📦 Next.js Bundle Analysis for langfuse-docs

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

New Page Added

The following page was added to the bundle from the code in this PR:

Page Size (compressed) First Load % of Budget (350 KB)
/docs/administration/billable-units 54.98 KB 459.78 KB 131.37%

Five Pages Changed Size

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

Page Size (compressed) First Load % of Budget (350 KB)
/docs/observability/data-model 60.52 KB 465.33 KB 132.95% (🟡 +0.32%)
/docs/observability/get-started 69.56 KB 474.37 KB 135.53% (🟡 +0.65%)
/docs/observability/overview 55.64 KB 460.44 KB 131.55% (🟢 -0.63%)
/docs/observability/sdk/python/overview 60.77 KB 465.57 KB 133.02% (🟡 +0.18%)
/docs/observability/sdk/typescript/instrumentation 66.72 KB 471.52 KB 134.72% (🟡 +0.25%)
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.

@Lotte-Verheyden Lotte-Verheyden marked this pull request as ready for review November 28, 2025 15:05
@dosubot dosubot bot added size:XL This PR changes 500-999 lines, ignoring generated files. documentation Improvements or additions to documentation labels Nov 28, 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:XL This PR changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants