Exporting your traces

Since Traceloop SDK is using OpenTelemetry under the hood, you can see everything in any observability platform that supports OpenTelemetry.

​

Traceloop

Go to Traceloop dashboard, click on the organization icon at the top right corner and select API Keys. Generate a new API key and copy it over. It won’t be shown again.

Set the API key as an environment variable in your app named TRACELOOP_API_KEY. For on-prem deployments, set TRACELOOP_API_ENDPOINT to the URL of your Traceloop instance.

Done! You’ll get instant visibility into everything that’s happening with your LLM. If you’re calling a vector DB, or any other external service or database, you’ll also see it in the Traceloop dashboard.

​

Datadog

With datadog, there are 2 options - you can either export directly to a Datadog Agent in your cluster, or through an OpenTelemetry Collector (which requires that you deploy one in your cluster).

See also Datadog documentation

Exporting directly to an agent is easiest. To do that, first enable the OTLP GRPC collector in your agent configuration. This depends on how you deployed your Datadog agent. For example, if you’ve used a Helm chart, you can add the following to your values.yaml (see this for other options):

otlp:
  receiver:
    protocols:
      grpc:
        enabled: true

Then, set this env var, and you’re done!

TRACELOOP_API_ENDPOINT=http://<datadog-agent-hostname>:4317

​

New Relic

Since New Relic natively supports OpenTelemetry, you just need to route the traces to New Relic’s endpoint and set the API key:

TRACELOOP_API_ENDPOINT=https://otlp.nr-data.net:443
TRACELOOP_HEADERS="api-key=<YOUR_NEWRELIC_LICENSE_KEY>"

for more information check out the docs link

​

Honeycomb

Since Honeycomb natively supports OpenTelemetry, you just need to route the traces to Honeycomb’s endpoint and set the API key:

TRACELOOP_API_ENDPOINT=https://api.honeycomb.io
TRACELOOP_HEADERS="x-honeycomb-team=<YOUR_API_KEY>"

​

SigNoz

​

With SigNoz cloud

Since SigNoz natively supports OpenTelemetry, you just need to route the traces to SigNoz’s endpoint and set the API key:

TRACELOOP_API_ENDPOINT=https://ingest.{region}.signoz.cloud
TRACELOOP_HEADERS="signoz-access-token=<SIGNOZ_INGESTION_KEY>"

Where region depends on the choice of your SigNoz cloud region:

Validate your configuration by following these instructions

​

With Self-Hosted version

Once you have an up and running instance of SigNoz, use the following environment variables to export your traces:

TRACELOOP_API_ENDPOINT="http://localhost:4317"