truefoundry-tracing

To add OpenTelemetry distributed tracing, you create a tracing project, install the Traceloop SDK, and instrument your application's entry point. Ensure Traceloop.init() runs at the very top of the entry file to capture spans.

Traces may not appear in the tracing dashboard if Traceloop.init() is not at the very top of the entry file, or if the TFY_BASE_URL and TFY_API_KEY environment variables are not correctly passed. A test request is also required to generate initial trace data.

Yes, TrueFoundry tracing supports capturing LLM calls and custom spans automatically. By installing the Traceloop SDK and instrumenting your app's entry point, the integration automatically captures LLM calls, workflows, and custom spans for observability.

For OpenTelemetry instrumentation with Traceloop, you must pass the TFY_BASE_URL and TFY_API_KEY via environment variables. You also need to include the X-TFY-TRACING-PROJECT-FQN header where applicable to ensure traces route correctly.

Yes, you can use OpenTelemetry tracing for Python and TypeScript apps within TrueFoundry deployment workflows. The setup process instruments your app's entry point to ensure traces are visible in the tracing dashboard after a test request.

The best way to instrument an entry point for distributed tracing is to ensure Traceloop.init() runs at the very top of the entry file. This allows the Traceloop SDK to automatically capture LLM calls and custom spans across your application workflows.