All integrations

Run agents with Datadog

Connect Datadog once, and every run that names it works in Datadog on the account you connected.

Connect DatadogOpens Settings → Connections in the console.

What an agent can do in Datadog

Investigate production with Datadog: search logs, metrics, traces, monitors, incidents and dashboards. US1 site; add another site as a custom server.

Jobs on Rush that use Datadog

How Datadog connects

Datadog is a remote MCP server, published by Datadog, at https://mcp.datadoghq.com/api/unstable/mcp-server/mcp. Connecting it signs in through the MCP OAuth flow on Datadog's side.

From Datadog: Datadog's MCP documentation.

Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.

After that, a run that names datadog in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.

POST https://api.phoenix.so/me/connections

{
  "type": "mcp",
  "name": "Datadog",
  "url": "https://mcp.datadoghq.com/api/unstable/mcp-server/mcp"
}

Whose Datadog account the agent uses

Your Datadog connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Datadog, and a run started with an API key uses the Datadog of the member who created the key.

To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Datadog, and that agent's runs use their account and nothing else: never yours, never another user's.

More Observability integrations

Frequently asked questions

How do I connect Datadog to Rush?

Open Settings → Connections in the console and connect Datadog, or send POST /me/connections with {"type":"mcp","name":"Datadog","url":"https://mcp.datadoghq.com/api/unstable/mcp-server/mcp"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.

Does every run get my Datadog account?

No. A run gets your Datadog connection only when it names it in connections ("connections": ["datadog"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.

What can an agent do in Datadog?

Investigate production with Datadog: search logs, metrics, traces, monitors, incidents and dashboards. US1 site; add another site as a custom server. 20 published jobs use it; this page lists them.

Can my app's users connect their own Datadog?

Yes. Make each user an agent from your template, and they sign in to their own Datadog through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.

Keep reading