Skip to main content

​
Overview

The Dash0 connector lets Rootly AI query your Dash0 environment during incident investigations. Dash0 is an OpenTelemetry-native observability platform, so this connector gives Rootly AI access to your traces, logs, metrics, service catalog, dashboards, and alerting — all through a single integration. Setup is a region selection followed by an OAuth authorization. There is no API key to create or paste.
Rootly AI’s access is read-only. It authorizes with a read scope and can query your Dash0 data but never create, modify, or delete dashboards, alerts, or check rules.

​
Before You Start

​
required
An account with access to the datasets you want Rootly AI to query. Rootly AI inherits the read access of whoever authorizes the connection.
​
required
Dash0 runs in multiple regions and your data lives in exactly one. You’ll pick this during setup, and picking the wrong one means Rootly AI authorizes against an instance that doesn’t hold your data.
​
required
Connecting a data source requires the permission to manage AI connectors on your Rootly account. If the Connect button is unavailable, ask a Rootly admin.
If you’re not sure which region you’re on, go to Settings → Endpoints in the Dash0 UI — the API URL shown there (e.g., api.us-west-2.aws.dash0.com) contains the region. Alternatively, check the region selector in the Dash0 app.

​
Connecting

1

Open the Dash0 Card

Go to Configuration → AI → Connectors and click Connect on the Dash0 card. The Connect Dash0 dialog opens.
2

Choose Your Region

​
dropdown
required
Select the region your Dash0 environment runs in:
  • US West 2 — api.us-west-2.aws.dash0.com (AWS Oregon)
  • EU West 1 — api.eu-west-1.aws.dash0.com (AWS Ireland)
  • EU Central 1 — api.eu-central-1.aws.dash0.com (AWS Frankfurt)
  • Europe West 4 — api.europe-west4.gcp.dash0.com (GCP Netherlands)
Selecting the wrong region sends Rootly’s queries to an instance that doesn’t contain your data.
3

Authorize

Click Connect Dash0. Rootly redirects to Dash0’s OAuth authorization flow — sign in if needed, review the requested access, and approve. Dash0 sends you back to Rootly, and the card flips to Connected.

​
What Rootly AI Can Read

Once connected, Rootly AI can query Dash0 for:
  • Traces — inspect distributed traces across your OpenTelemetry-instrumented services.
  • Logs — search and filter across your ingested log streams.
  • Metrics — query metrics via PromQL, including Dash0’s synthetic metrics (dash0.spans, dash0.logs).
  • Service catalog — list all services with health indicators (request rates, error percentages, latency P95), resource types, and inter-service dependencies.
  • Dashboards — look up dashboard configurations to correlate what humans typically monitor with what’s happening in the incident.
  • Check rules & failed checks — list alerting rules and active/historical check failures.
  • Kubernetes — query pod status and metadata for K8s-instrumented workloads.
  • Synthetic checks — check the status and results of synthetic monitors.
Access is scoped by the permissions on the authorizing Dash0 account.

​
During an Incident

“Error rate on the checkout service jumped to 4.2% at 2:14pm. The service graph shows it depends on payment-api, which started returning 503s two minutes earlier.” Rootly AI queries Dash0 for the service catalog, traces, logs, and metrics correlated with the current incident. When error rates spike, latency degrades, or dependencies start failing, Rootly AI surfaces the exact service, dependency chain, and correlated signals — no manual dashboard-hunting required. Because Dash0 is OpenTelemetry-native, the service catalog includes automatically discovered inter-service dependencies derived from your trace data. Rootly AI uses these dependencies for blast-radius analysis — understanding which upstream and downstream services are affected by an incident.

​
Best Practices

  • Authorize with a service account, not a personal one. If a personal Dash0 account leaves the organization, the integration silently breaks the next time it’s queried. A service account with stable membership avoids that.
  • Verify region selection before authorizing. Wrong-region is the #1 setup failure. Double-check the region against your actual Dash0 URL before hitting Connect.
  • Ensure your services emit OpenTelemetry traces. Dash0’s service catalog and dependency map are built from trace data. Services that only emit metrics or logs will appear in the catalog but won’t have dependency information.
  • Test with /rootly test. After connecting, declare a test incident and confirm Rootly AI can pull Dash0 signals during the investigation.

​
Troubleshooting

Common causes: (1) the authorizing user doesn’t have permission to grant third-party access in Dash0 — check with a Dash0 admin; (2) your organization has restricted third-party grants at the workspace level.
You authorized against a Dash0 region that doesn’t contain your data. Disconnect the integration, reconnect against the correct region, and re-authorize. There’s no way to migrate a wrong-region connection; you have to disconnect and start over.
Dependencies are inferred from OpenTelemetry trace data. If your services only emit metrics or logs (no traces), Dash0 can’t observe inter-service calls. Ensure your services are instrumented with an OpenTelemetry SDK or auto-instrumentation agent that emits spans.
Two common causes:
  1. Authorizer permissions — Rootly AI inherits the access of whoever authorized the connection. If the authorizing Dash0 account can only see certain datasets or services, Rootly AI has the same limitation. Re-authorize with a broader account to fix.
  2. Missing telemetry — Rootly AI auto-discovers all datasets and ingests from each. If a service isn’t appearing in any dataset, verify it’s instrumented and sending data to Dash0.

​
Frequently Asked Questions

No. The connector uses OAuth 2.0 — you authorize through Dash0’s consent screen, and Rootly AI receives a scoped access token. No API key to create or paste.
One Dash0 connector per Rootly team currently. If you operate across multiple regions, connect the one that hosts most of your observability signal.
Rootly AI queries Dash0 fresh on each investigation call and does not maintain a persistent copy of your Dash0 data. However, query results do appear in the LLM traces Rootly logs for quality monitoring — the same as every other tool call. See Data Privacy for Rootly AI for retention details.
Dash0 supports all four OTel signals: traces, metrics, logs, and profiles. Rootly AI can query traces, metrics, and logs through the connector.
The connector gives Rootly AI read access to your Dash0 data through Dash0’s MCP tools. Agent0 (Dash0’s own AI assistant) is a separate feature — the two don’t interact.

Connectors Overview

The full list of Connectors and how they fit together.

Honeycomb Connector

Another OTel-native observability connector — similar setup flow.

Data Privacy for Rootly AI

What Rootly AI sees, retention, and model-training controls.