Skip to main content
Two catalog agents investigate a regression through application performance telemetry: Datadog Investigator and Grafana Investigator. Both run the same aggregate → pivot → trace flow — narrow on the failing slice, read the flame graph of one bad trace within it, correlate against deploys — and return structured findings with a deeplink on every claim. Both are strictly read-only. Neither can mute a monitor, silence an alert, close an incident or edit a dashboard.

​
Datadog Investigator

Localises a regression across Datadog’s own telemetry, with a Datadog permalink on every finding so the claim and its evidence stay together when the report is read by someone who was not on the run. Before you deploy — model access, a Datadog connection with read-only access to all five sources, and an integration group, because the agent reaches Datadog through a group-scoped gateway endpoint.
An account can hold several Datadog connections. Provider presence alone does not identify the organization or environment you meant, so select the specific connection this agent should use rather than assuming the only active one is right.
Where it stops. It is bounded by what Datadog holds. If the relevant span was sampled away or the log retention window has passed, it reports that it could not verify the step rather than filling the gap by inference.

​
Grafana Investigator

Correlates metrics against logs, traces and profiles across the Grafana stack, returning findings with Grafana deeplinks so each claim can be checked. Before you deploy — model access, and one of three paths to Grafana:
The Grafana connection is optional because the second path replaces it: a self-hosted agent pointed at your own in-cluster server needs no connection. Add one only to use the built-in tooling.
The wizard asks where the agent runs and then disables the paths that target does not support, rather than hiding them — so a choice that is unavailable is visibly unavailable. Where it stops. Bounded by retention and by what its path can reach. A self-hosted agent pointed at your own in-cluster server sees exactly what that server exposes, and it reports an unreachable data source rather than working around it.

​
Next steps

Agent catalog

Every deployable agent, and what each one is for.

Cloud providers

The AWS, Azure and Google Cloud investigators.

Integrations list

Connecting Datadog and Grafana.

Integration groups

The group-scoped gateway endpoint the Datadog agent needs.