Integration · Developer
AI agents for Datadog
Post events to the Datadog Event Explorer and send custom metric points, on any Datadog site, with an API key.
- Actions
- 2
- Read
- 0
- Write
- 2
Actions
What your agents can do in Datadog
2 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 0
Look things up. Nothing changes.
This tool has no read actions.
Write 2
Create, change or send.
Post an event
Posts an event to the Datadog Event Explorer, like a deploy, a config change or an alert from another system, with optional tags, a host, an alert type (error, warning, info, success) and a priority.
Submit a metric point
Sends one data point of a custom metric, like a queue length or the number of orders, with optional tags, a host and a unit.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Datadog account.
What you enter
- API key
Settings
- Datadog site
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Let an agent update Datadog
Have the agent post an event or submit a metric point in Datadog as part of a larger task. Turn on approval and a person signs off on each change first.
- 02
Share what it finds in Slack
Give one agent Datadog and Slack: it can post an event in Datadog and post a summary to a Slack channel in the same run.
- 03
Run it as a workflow step
Add "Post an event" to a workflow, and it runs in Datadog the same way every time, with or without an agent.
Works well with
More Developer tools
- GitHub4 actionsOpen and comment on issues, and start GitHub Actions workflows, in the repositories a personal access token can reach.
- GitLab4 actionsOpen and comment on issues, and start CI/CD pipelines, in the GitLab.com projects an access token can reach.
- Bitbucket3 actionsComment on and read pull requests, and start Bitbucket Pipelines, in the Bitbucket Cloud repositories your Atlassian API token can reach.
- Sentry3 actionsList, read, resolve and ignore error issues in a sentry.io organization, in its US or EU (Germany) data region.
- PagerDuty4 actionsOpen, acknowledge and resolve PagerDuty incidents, add notes to them, and see who is on call for a schedule.
- App Store Connect8 actionsLook after iPhone, iPad and Mac apps on Apple's App Store.
FAQ
Datadog and MyDeepAgents
Can MyDeepAgents connect to Datadog?
Yes. The Datadog connector has 2 actions, each of which makes a change. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Datadog?
Paste an API key from your Datadog account. You'll need: API key. The connection also asks for: Datadog site. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Datadog without asking?
Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs.
Can I use Datadog in workflows as well as agents?
Yes. Every Datadog action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Datadog to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.