Thanks to visit codestin.com
Credit goes to github.com

Skip to content

docs: Add Langfuse cloud integration documentation#1384

Draft
Alan-Cha wants to merge 1 commit into
mainfrom
langfuse-docs-clean
Draft

docs: Add Langfuse cloud integration documentation#1384
Alan-Cha wants to merge 1 commit into
mainfrom
langfuse-docs-clean

Conversation

@Alan-Cha
Copy link
Copy Markdown
Contributor

Summary

Comprehensive documentation for integrating Kagenti with Langfuse cloud for LLM observability.

What's Included

  • docs/langfuse-integration.md (650+ lines) - Complete integration guide covering:

    • Langfuse cloud account setup and API key generation
    • OTEL collector configuration for trace export
    • Agent instrumentation with GenAI semantic conventions
    • Testing procedures and troubleshooting
    • Cost tracking explanation
    • Comparison with self-hosted Phoenix
  • deployments/envs/langfuse-cloud-values.yaml.example - Helm values template for OTEL configuration

  • Updated README.md - Fixed Langfuse typo and added LLM Observability section

  • Updated .gitignore - Protected actual API keys from being committed

Why Langfuse Cloud?

Self-hosted Langfuse v3 requires ClickHouse, which is incompatible with nested virtualization on Mac M1 (Kind/Rancher). Cloud solution provides:

  • ✅ No infrastructure management
  • ✅ Free tier for development
  • ✅ Production-ready observability
  • ✅ Works from any cluster

Testing

Tested with weather agent demo - traces successfully flow to Langfuse cloud dashboard with automatic cost tracking and GenAI semantic convention support.

Related

Addresses requirements for LLM observability integration with Kagenti platform.


Branch: langfuse-docs-clean
Commit: 455d7a1

Add comprehensive documentation for integrating Kagenti with Langfuse cloud
service for LLM observability and trace collection.

## What's Added

- docs/langfuse-integration.md: Complete integration guide including:
  - Langfuse cloud account setup instructions
  - API key generation and configuration
  - OTEL collector configuration for trace export
  - Agent instrumentation with GenAI semantic conventions
  - Testing and verification procedures
  - Cost tracking explanation
  - Troubleshooting guide

- deployments/envs/langfuse-cloud-values.yaml.example: Helm values template
  for configuring OTEL collector to export traces to Langfuse cloud

- README.md: Updated observability section to reference Langfuse (fixed typo:
  Langflow -> Langfuse) and added LLM Observability documentation links

- .gitignore: Added langfuse-cloud-values.yaml to prevent committing API keys

## Why Langfuse Cloud vs Self-Hosted

Attempts to deploy Langfuse v3 self-hosted on Mac M1 with Kind/Rancher failed
due to ClickHouse compatibility issues with nested virtualization. ClickHouse
hangs during startup in the Mac M1 -> Podman/Lima -> Kind -> ClickHouse stack.

Langfuse cloud provides:
- No infrastructure management (no ClickHouse, Redis, PostgreSQL, MinIO, Worker)
- Works from any cluster (Kind, cloud, OpenShift)
- Free tier available (Hobby plan, no credit card)
- Production-ready with automatic scaling and HA

## Cleanup

Removed temporary investigation/research markdown files that were used during
debugging but should not be in the main repository:
- ARCHITECTURE_EXPLAINED.md
- CLICKHOUSE_*.md (3 files)
- END_TO_END_SUCCESS.md
- LANGFUSE_*.md (4 files)
- PODMAN_COMPOSE_SUCCESS.md

These were interim documentation files created during troubleshooting and are
not needed for the final integration documentation.

Resolves investigation into LLM observability options for Kagenti on Mac M1
development environments.

Signed-off-by: Alan Cha <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: New /:ToDo

Development

Successfully merging this pull request may close these issues.

1 participant