> ## Documentation Index
> Fetch the complete documentation index at: https://docs.komodor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# APM

> The read-only investigators for Datadog and Grafana — what each reads, the paths available to reach it, and where each stops.

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.

| Source           | What it uses it for                                                 |
| ---------------- | ------------------------------------------------------------------- |
| Traces and spans | Localising the failing slice, then the flame graph of one bad trace |
| Logs             | The error text behind a failure, scoped to the slice                |
| Metrics          | Rates, latencies and saturation across the incident window          |
| Monitors         | What alerted, when it transitioned, and what it was watching        |
| Events           | Deploys and changes to correlate the regression against             |

**Before you deploy** — model access, a Datadog connection with read-only access to all five
sources, and an [integration group](/manage-your-agents/build/integration-groups), because the agent
reaches Datadog through a group-scoped gateway endpoint.

<Note>
  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.
</Note>

**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.

| Source               | What it uses it for                                                        |
| -------------------- | -------------------------------------------------------------------------- |
| Prometheus           | Rates, latencies and saturation across the incident window                 |
| Loki                 | The error text behind a failure, scoped to the failing slice               |
| Tempo                | Traces, and the flame graph of one bad trace                               |
| Pyroscope            | Profiles, when the regression is in CPU or memory rather than a dependency |
| Alerts and incidents | What fired, when, and what it was watching                                 |
| Annotations          | Deploys and changes to correlate against                                   |
| Sift                 | Grafana's own automated investigations, where they have already run        |

**Before you deploy** — model access, and one of three paths to Grafana:

| Path                           | How it works                                                                                                      | Offered for       |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------- | ----------------- |
| **Built-in Grafana tooling**   | The agent talks to Grafana Cloud or your own Grafana over a stored connection. Komodor is never in the data path. | Either deployment |
| **Your own in-cluster server** | The agent uses an MCP server you already run, holding its own Grafana credentials. Nothing is stored in Komodor.  | Self-hosted       |
| **The MCP Gateway**            | The gateway is bound to a registered remote MCP server, such as Grafana Cloud's own endpoint.                     | Komodor cloud     |

<Note>
  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.
</Note>

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

<CardGroup cols={2}>
  <Card title="Agent catalog" href="/manage-your-agents/build/catalog/overview">
    Every deployable agent, and what each one is for.
  </Card>

  <Card title="Cloud providers" href="/manage-your-agents/build/catalog/cloud-providers">
    The AWS, Azure and Google Cloud investigators.
  </Card>

  <Card title="Integrations list" href="/manage-your-agents/build/built-in-integrations">
    Connecting Datadog and Grafana.
  </Card>

  <Card title="Integration groups" href="/manage-your-agents/build/integration-groups">
    The group-scoped gateway endpoint the Datadog agent needs.
  </Card>
</CardGroup>


## Related topics

- [Kubernetes](/manage-your-agents/build/catalog/kubernetes.md)
- [Agent catalog](/manage-your-agents/build/catalog/overview.md)