Skip to main content

Dash0

Overview​

Dash0 sends logs, metrics, and traces to Dash0 using the OpenTelemetry Protocol (OTLP). The Praxis Dash0 destination is a catalog node for the same OTLP-based export path as the generic OTLP destination — configured with Dash0's OTLP-native ingress and conventions.

Supported types: Logs · Metrics · Traces

Configuration​

The Dash0 destination form uses Dash0's own terminology — you'll normally only fill Region, Dataset, and Protocol, and attach an Auth Token credential. Praxis automatically translates these into the standard OTLP collector exporter config (endpoint + headers + auth) that Dash0 expects. Advanced overrides for every OTLP knob (TLS, queues, retries, per-signal endpoints) are available under the collapsed gRPC Override / HTTP Override groups — see OTLP destination for their full parameter list.

Primary fields​

  • Region. Dash0 regional deployment (e.g. eu-west-1, us-west-2), taken from your Dash0 organization's ingress endpoint. Praxis derives the collector endpoint as ingress.<region>.aws.dash0.com automatically. For custom ingress hosts, leave Region empty and use the override under gRPC Override / HTTP Override.
  • Dataset. Optional. Target Dash0 Dataset. When set, Praxis sends a Dash0-Dataset: <dataset> header. Leave empty to route to the organization's default dataset (Dash0 handles default routing implicitly; no header is sent).
  • Protocol. grpc (recommended) or http. Dash0 supports both OTLP/gRPC (derived port 4317) and OTLP/HTTP (derived port 4318).
  • Auth Token. Attach a bearer token credential holding your Dash0 Auth Token (generated under Organization → Auth Tokens in Dash0). Praxis sends it as Authorization: Bearer <Auth Token> on every OTLP request.

Advanced​

  • Ingress Endpoint Override. Optional. Leave empty when Region is set. Use this for custom ingress hosts, e.g. ingress.eu-west-1.aws.dash0.com:4317 (gRPC) or https://ingress.eu-west-1.aws.dash0.com:4318 (HTTP). A value here always wins over Region.
  • gRPC / HTTP Headers (advanced). Additional headers sent with every request. You normally do not need to set Dash0-Dataset here — use the top-level Dataset field. A header set here overrides the Dataset field.
  • TLS. Dash0 ingress is TLS-only. Defaults are strict (insecure = false). Do not turn these off for production ingress.
  • Compression. gzip is the default for both gRPC and HTTP.

External documentation​