Use Datadog with Evergreen

The Datadog integration lets the agent investigate with your own Datadog access. It searches logs, queries metrics, and looks at monitors while it works on a task, and it has the permissions your Datadog account has.

What the agent can do

• Search and analyze logs, spans, and RUM events.
• Query metrics, monitors, SLOs, and incidents.
• Read and triage error-tracking issues.
• Inspect dashboards, notebooks, and the service catalog.
• Look into database monitoring, Kubernetes, LLM Observability, CI pipelines and tests, synthetic tests, and profiles.
• Use Datadog’s own skills, which guide how it writes its queries.

Charts the agent pulls from Datadog appear in the session. It cites the Datadog links it relied on when it reports back.

Who can connect it

An Owner or Admin installs it for the workspace. Then each person connects their own Datadog account. Datadog signs in on its own, so there’s no app to create. If your Owners and Admins have turned on Members can connect integrations that need no setup, a member can connect without waiting for an install. See How integrations work for that setting.

Your Datadog role needs the mcp_read and mcp_write permissions, plus the usual permissions for what the agent reads. For example, searching monitors needs Monitors Read, just as it does in Datadog. The Standard role has both MCP permissions.

Datadog regions

Datadog keeps each region separate, so you connect to the one your account lives in. The catalog lists these.

When you connect, Evergreen asks which region you sign in to. If your workspace offers only one region, it doesn’t ask. To change which regions people can pick, an Owner or Admin edits Regions offered and Default region in the settings on the Overview tab of Manage. If you use more than one region, connect each one separately. Once you’ve connected one, the Datadog row’s button reads Add region.

Connect Datadog

What it asks before changing things

While the agent plans, it reads. Creating or changing Datadog resources, such as monitors, becomes available once you approve the plan, or from the start if you skip the plan. The agent is told to create or change things only when the task asks. See Plans and asks for how approval works.

Datadog has its own switch as well. In your Datadog organization settings, MCP Write Access is off by default, and it gates all write tools for everyone, no matter their role. An Owner or Admin in Evergreen can also block individual tools for everyone on the Tools tab in Manage.

Start sessions from Datadog monitors

An automation can start a session when a Datadog monitor alerts, warns, stops reporting data, or recovers. The session can reply under the monitor’s own Slack alert. To connect a monitor to an automation, Evergreen edits the monitor as you, so you need your own Datadog connection first. If you don’t have one, the automation shows Connect Datadog to wire it. See Start sessions automatically to set one up.

Limits

• The agent sees what your Datadog account can see.
• Datadog’s US government site isn’t in the list of regions.
• Evergreen offers the groups of Datadog tools that sessions use. Tools for security, cost, networks, feature flags, cases, and workflows aren’t offered unless whoever runs your Evergreen adds them.
• Disabling the Datadog Generic MCP Client row in Datadog’s Organization Settings › Mobile and Third-Party Access switches off all the apps in your Datadog organization that registered themselves, not only Evergreen. To remove one person’s grant, revoke it from that row.

Troubleshooting