Developer tools
Datadog for AI agents.
Managed auth, ready-made tools.
Search logs, query metrics, check monitors and incidents, and schedule downtimes in your users' Datadog organizations.
About Datadog
With the Datadog connector, your agent investigates in each user’s own Datadog organization through Agent200: it searches logs, queries metrics, checks monitors, events and incidents, and can schedule a downtime or open an incident. Every user connects their own account through managed OAuth.
Datadog is an observability platform that brings metrics, logs, traces and alerts from your infrastructure and applications into one place.
Tools
What your agent can do in Datadog.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Datadog connection.
-
Search logs
Readdatadog_search_logsFind log events that match a query in a time range.
-
Query metrics
Readdatadog_query_metricsRead timeseries points for a metric query.
-
List monitors
Readdatadog_list_monitorsList monitors and their current state.
-
Schedule a downtime
Writedatadog_create_downtimeSilence alerts from chosen monitors for a period.
-
Search events
Readdatadog_search_eventsFind events such as deploys and alerts in a time range.
-
List incidents
Readdatadog_list_incidentsList incidents with their severity and state.
-
Create an incident
Writedatadog_create_incidentDeclare an incident with a title and severity.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Datadog, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let your agent search logs and metrics, and switch off
datadog_create_downtimeanddatadog_create_incidentif it should observe but never act. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use. A call outside them is refused.
Get started
Connect Datadog
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Datadog
Each end user authorizes their own Datadog account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Datadog account, once. const connection = await agent200 .user("user_123") .connect("datadog"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Datadog tools
Name the user, the model and the tools. The model decides which Datadog tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Which monitors are alerting right now", tools: ["datadog"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Datadog's own page. You never see or store their Datadog password.
-
What access is requested
Datadog lists the scopes requested, such as reading logs, metrics and monitors. The user must already hold the Datadog permissions for each scope, so the agent never gets more than that user has.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Datadog connector and how to use it.
Connector: Datadog, through Agent200. In code: "datadog". What it does: Search logs, query metrics, check monitors and incidents, and schedule downtimes in your users' Datadog organizations. Page: https://www.agent200.com/tools/datadog/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Datadog's own page, through the authorization link Agent200 returns. Never ask a user for a Datadog password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: datadog_search_logs, datadog_query_metrics, datadog_list_monitors, datadog_search_events, datadog_list_incidents. Write tools: datadog_create_downtime, datadog_create_incident. Name "datadog" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/tools/datadog/framework/claude/ https://www.agent200.com/tools/datadog/framework/chatgpt/ https://www.agent200.com/tools/datadog/framework/claude-code/ https://www.agent200.com/tools/datadog/framework/muse/ https://www.agent200.com/tools/datadog/framework/grok-bot/ https://www.agent200.com/tools/datadog/framework/openai-dots/ https://www.agent200.com/tools/datadog/framework/claude-duet/ https://www.agent200.com/tools/datadog/framework/hermes-agent/ https://www.agent200.com/tools/datadog/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /tools/datadog.md
Guides
Use Datadog with the AI you build on.
Step-by-step setup for Datadog with a specific model, assistant or agent framework.
-
Datadog + Claude
How to connect Datadog to Claude
-
Datadog + ChatGPT
How to connect Datadog to ChatGPT
-
Datadog + Claude Code
How to connect Datadog to Claude Code
-
Datadog + Muse
How to connect Datadog to Muse
-
Datadog + Grok Bot
How to connect Datadog to Grok Bot
-
Datadog + OpenAI Dots
How to connect Datadog to OpenAI Dots
-
Datadog + Claude Duet
How to connect Datadog to Claude Duet
-
Datadog + Hermes Agent
How to connect Datadog to Hermes Agent
-
Datadog + OpenClaw
How to connect Datadog to OpenClaw
FAQ
Datadog and Agent200, answered.
Who handles the Datadog OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Datadog.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Datadog connection, never another user's. It cannot reach anything the user or Datadog has not authorized.
Can I limit what my agent can do in Datadog?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.