Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.uselemma.ai/llms.txt

Use this file to discover all available pages before exploring further.

No traces in Lemma

  • Confirm startup instrumentation executed before app traffic.
  • Verify LEMMA_BASE_URL is https://api.uselemma.ai/otel/v1/traces, and LEMMA_API_KEY and LEMMA_PROJECT_ID are set.
  • Confirm there are no network egress blocks to the Lemma OTLP endpoint.

Traces in Langfuse but not Lemma

  • Verify the Lemma exporter is attached to LangfuseSpanProcessor.
  • Validate request headers (Authorization, X-Lemma-Project-ID).
  • Check for exporter errors in runtime logs.

Existing OTel traces not appearing in Lemma

  • Confirm your existing OpenTelemetry-compatible instrumentation is creating spans.
  • Confirm Lemma is configured as an OTLP trace export destination on your tracer provider or collector.
  • Verify the Lemma endpoint and headers are set on that exporter.

Missing child spans

  • Validate framework/provider instrumentation is enabled in Langfuse or your existing OpenTelemetry stack.
  • Ensure instrumentation initializes before provider clients are instantiated.

Data appears delayed

  • For short-lived/serverless handlers, call forceFlush() at request end.