langfuse-observability

Monitor Langfuse v3.x metrics on EKS with OpenTelemetry.

18|4|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/aws-samples/sample-oh-my-aidlcops --skill langfuse-observability-aws-samples
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: langfuse-observability
Source: https://github.com/aws-samples/sample-oh-my-aidlcops/tree/main/plugins/ai-infra/skills/langfuse-observability
Command: npx skills add https://github.com/aws-samples/sample-oh-my-aidlcops --skill langfuse-observability-aws-samples

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires OpenTelemetry Collector, PostgreSQL, ClickHouse, Redis, S3, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Langfuse-observability provides a comprehensive solution for tracking token cost, latency, and quality scores for Langfuse operations on EKS, using OpenTelemetry and various backends.

Core Features & Use Cases

  • End-to-End Trace Tracking: Captures traces from vLLM, Bifrost/LiteLLM, and LangChain agents.
  • Self-Hosted Backends: Supports PostgreSQL, ClickHouse, Redis, and S3 for data storage.
  • Use Case: Ideal for organizations that require detailed observability into Langfuse operations for regulatory compliance or performance optimization.

Quick Start

Set up Langfuse-observability by executing the provided script and configuring your environment for OpenTelemetry integration.

Frequently Asked Questions about langfuse-observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track token cost and latency for Langfuse operations on EKS?

You can track Langfuse token cost and latency on EKS by integrating OpenTelemetry to collect operational metrics and traces. This approach monitors token usage, tracks quality scores, and captures traces from vLLM and LangChain agents.

What storage backends can I use for self-hosted Langfuse observability data?

Self-hosted Langfuse observability data supports PostgreSQL, ClickHouse, Redis, and S3 as storage backends. These dependencies store collected traces, token costs, and quality scores for your operations.

Does Langfuse observability capture traces from vLLM and LangChain agents?

Yes, Langfuse observability captures end-to-end traces from vLLM, Bifrost/LiteLLM, and LangChain agents. The Skill integrates OpenTelemetry to track these traces alongside token costs and latency metrics on EKS.

Do I need an OpenTelemetry Collector to set up Langfuse monitoring on EKS?

Yes, an OpenTelemetry Collector is required to set up Langfuse monitoring on EKS. It serves as the core dependency for integrating OpenTelemetry to track traces, token costs, and quality scores.

When should I use self-hosted Langfuse observability for my LLM applications?

You should use self-hosted Langfuse observability when your organization requires detailed tracking of token costs, latency, and quality scores for regulatory compliance or performance optimization on EKS.