Revise Langfuse integration guide for Quarkus

[edeandrea]

Updated the integration guide for Langfuse with Quarkus LangChain4j to include the Quarkus Langfuse extension and improved clarity in configuration steps.

Greptile Summary

This PR revises the Quarkus LangChain4j integration guide to lead with the new quarkus-langfuse Quarkiverse extension instead of manual OpenTelemetry configuration, significantly simplifying the setup steps from ~5 config properties down to 3. The old manual OTel approach is preserved as a "Manual Configuration" appendix.

• New primary path: Adds quarkus-langfuse as the recommended dependency, documents the three application.properties keys (base-url, username, password), and lists everything the extension auto-configures (OTLP endpoint, auth headers, span filtering, prompt/completion tracing, DevServices support).
• Frontmatter not updated: The page title and description still say "Using OpenTelemetry", which no longer reflects the primary approach described in the guide.
• Minor copy issues: A word-boundary typo ("toyour") on line 23 and a brand-name capitalisation regression ("LangFuse" → should be "Langfuse") in the code example on line 94.

Confidence Score: 4/5

Safe to merge after addressing the three small copy issues — none affect runtime behaviour.

The content changes are accurate and well-structured. The only issues are a typo ("toyour"), a brand-name capitalisation regression in the code sample ("LangFuse" instead of "Langfuse"), and frontmatter that still advertises the OpenTelemetry-first approach the guide has just moved away from. All three are easy one-line fixes.

content/integrations/frameworks/quarkus-langchain4j.mdx — frontmatter title/description, line 23 typo, and line 94 capitalisation.

Sequence Diagram

sequenceDiagram
    participant App as Quarkus App
    participant Ext as quarkus-langfuse extension
    participant OTel as OTel SDK (quarkus-opentelemetry)
    participant LF as Langfuse Cloud / Self-hosted

    App->>OTel: AI call (ChatModel invocation)
    OTel->>Ext: "Span produced (gen_ai.* attributes)"
    Ext->>Ext: Filter spans (AI_ONLY mode), set input/output attributes
    Ext->>LF: Export via OTLP/HTTP (Basic auth)
    LF-->>App: Traces visible in Langfuse UI

    note over Ext,LF: In dev/test mode, DevServices auto-starts a local Langfuse instance

Loading

Prompt To Fix All With AI

Fix the following 3 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 3
content/integrations/frameworks/quarkus-langchain4j.mdx:23
Missing space between "to" and "your" — "toyour" is a typo.

```suggestion
Add the `quarkus-opentelemetry` and `quarkus-langfuse` dependencies to your `pom.xml` (Gradle users can include equivalent coordinates in Gradle):
```

### Issue 2 of 3
content/integrations/frameworks/quarkus-langchain4j.mdx:94
The product name is "Langfuse" (not "LangFuse"). Every other occurrence in the document and across the repo uses the lowercase-f form. This diff introduced the capitalisation change — worth reverting so the example stays consistent with the brand name.

```suggestion
        System.out.println(service.writeAPoem("Langfuse", 4));
```

### Issue 3 of 3
content/integrations/frameworks/quarkus-langchain4j.mdx:2-5
The frontmatter `title` and `description` still describe the integration as primarily OpenTelemetry-based ("Using OpenTelemetry"), but the guide now leads with the `quarkus-langfuse` extension and pushes raw OTel configuration to a "Manual Configuration" appendix. A reader landing on this page from a search or sidebar will see a misleading title.

```suggestion
title: Integrating Langfuse with Quarkus LangChain4j
sidebarTitle: Quarkus LangChain4j
logo: /images/integrations/langchain4j_icon.svg
description: Learn how to integrate Langfuse with Quarkus LangChain4j using the Quarkus Langfuse extension for enhanced observability and performance monitoring in your AI applications.
```

_{Reviews (1): Last reviewed commit: "Revise Langfuse integration guide for Qu..." | Re-trigger Greptile}

[claude]

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

[vercel]

@edeandrea is attempting to deploy a commit to the langfuse Team on Vercel.

A member of the Team first needs to authorize it.