langfuse-multi-env-setup

# Langfuse Multi-Environment Setup ## Overview Configure Langfuse across dev/staging/production with isolated API keys, environment-specific SDK settings, secret management, and CI/CD integration to prevent cross-environment data leakage. ## Prerequisites - Separate Langfuse API key pairs per environment (or separate projects) - Secret management solution (env vars, Vault, AWS/GCP secrets) - CI/CD pipeline with environment-aware deployment ## Environment Strategy | Environment | API Key Source | Langfuse Project | Settings | |-------------|---------------|-----------------|----------| | Development | `.env.local` | Dev project | Debug on, flush immediately, 100% sampling | | Staging | CI/CD secrets | Staging project | Prod-like settings, 50% sampling | | Production | Secret manager | Prod project | Optimized batching, 10% sampling | ## Instructions ### Step 1: Environment-Specific Configuration ```typescript // src/config/langfuse.ts import { LangfuseSpanProcessor } from "@langfuse/otel"; import { NodeSDK } from "@opentelemetry/sdk-node"; import { LangfuseClient } from "@langfuse/client"; type Env = "development" | "staging" | "production"; interface LangfuseEnvConfig { exportIntervalMillis: number; maxExportBatchSize: number; debug: boolean; sampleRate: number; } const ENV_CONFIGS: Record<Env, LangfuseEnvConfig> = { development: { exportIntervalMillis: 1000, maxExportBatchSize: 1, debug: true, sampleRate: 1.0, }, staging: { exportI...