LangGraph Multi-Exporter Span Processing Bottleneck
warningResource ContentionUpdated Jul 9, 2025
Multiple OpenTelemetry exporters (Jaeger, Last9, console) processing the same LangGraph spans independently cause lag, memory pressure from overloaded buffers, and missing data when one exporter blocks the shared processing pipeline.
How to detect:
Detect multiple BatchSpanProcessor or SimpleSpanProcessor instances registered simultaneously. Monitor for span export lag increasing over time, memory growth in span buffers, or partial span data appearing in some backends but not others.
Recommended action:
Use single OTLP exporter for production (typically to Last9) and limit additional exporters to local development environments. Remove redundant BatchSpanProcessor registrations and use environment variable gating (e.g., if ENVIRONMENT == development) for console exporters.