Dash0

Documentation Index

Fetch the complete documentation index at: https://www.truefoundry.com/llms.txt

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

​

What is Dash0?

​

Key Features of Dash0

• OpenTelemetry Native: Accepts traces, metrics, and logs directly via OTLP/HTTP and OTLP/gRPC with no proprietary instrumentation required.
• Distributed Tracing: Visualize end-to-end request flows across services with full span detail and trace timelines.
• Datasets: Route telemetry to named datasets for logical separation of environments, teams, or signal types.
• Alerting: Set threshold-based alerts on trace latency, error rates, and custom metrics.

​

Prerequisites

1. TrueFoundry Account: Create a TrueFoundry account and follow the instructions in our Gateway Quick Start Guide.
2. Dash0 Account: Sign up at app.dash0.com. A free trial is available.
3. Dash0 Auth Token: Create an auth token with Ingest permissions from Organization Settings → Auth Tokens.
4. Dash0 OTLP Endpoint: Find your region-specific endpoint from Organization Settings → Endpoints → OTLP via HTTP.

​

Understanding the Dash0 Endpoint

https://ingress.<region>.aws.dash0.com

• US West 2: https://ingress.us-west-2.aws.dash0.com/v1/traces
• EU West 1: https://ingress.eu-west-1.aws.dash0.com/v1/traces

​

Integration Steps

1

Get Your Dash0 Endpoint and Auth Token

1. Log in to app.dash0.com.
2. Go to Organization Settings → Endpoints → OTLP via HTTP and copy the base endpoint URL.
3. Go to Organization Settings → Auth Tokens.
4. Click Add to create a new token, give it a name (for example tfy-gateway), set Signal types to All signal types, and set Permissions to Ingesting.
5. Copy the token value immediately — Dash0 will not show it again.

Dash0 auth tokens start with auth_. The token shown in the Auth Tokens list is masked — copy it immediately after creation as you cannot retrieve it later.

2

Configure OTEL Export in TrueFoundry

1. Go to AI Gateway → Controls → Settings in the TrueFoundry dashboard.
2. Scroll down to the OTEL Config section and click the edit (✏️) button.

3. Enable the Otel Traces Exporter Configuration toggle and fill in:

Field	Value
Toggle	Enabled
Protocol	HTTP Configuration
Endpoint	https://ingress.<your-region>.aws.dash0.com/v1/traces
Encoding	Proto
Header Key 1	Authorization
Header Value 1	Bearer <your-dash0-auth-token>
Header Key 2	Dash0-Dataset
Header Value 2	default

4. Enable the Otel Metrics Exporter Configuration toggle and fill in:

Field	Value
Toggle	Enabled
Protocol	HTTP Configuration
Endpoint	https://ingress.<your-region>.aws.dash0.com/v1/metrics
Encoding	Proto
Header Key 1	Authorization
Header Value 1	Bearer <your-dash0-auth-token>
Header Key 2	Dash0-Dataset
Header Value 2	default

5. Click Save to apply the configuration.

Replace <your-region> with your actual Dash0 region (for example us-west-2 or eu-west-1). Both the traces and metrics exporters require two headers: the Authorization header with your Bearer token and the Dash0-Dataset header to route data to the correct dataset. Using default routes to your organization’s default dataset.

3

Verify the Integration

1. Make a request through the TrueFoundry AI Gateway (for example from the Playground).
2. Log into app.dash0.com and click Tracing in the left sidebar.
3. Click All Traces and confirm traces from tfy-llm-gateway are appearing.

4. To verify metrics, click Metrics in the left sidebar and query for tfy_ prefixed metric names.

If no traces appear after sending a request, try toggling the Otel Traces Exporter Configuration off and back on in TrueFoundry and saving again. This forces the gateway to reload the exporter configuration without requiring a full pod restart.

​

Configuration Reference