Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 16 additions & 10 deletions config/_default/menus/main.en.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2769,12 +2769,24 @@ menu:
parent: case_management
identifier: case_management_troubleshooting
weight: 7
- name: Action Interface
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What exactly is this changing for Action Interface? Was it not shown in the nav before? It's not a feature we want to promote.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was rearranging the sidebar to match the way features are arranged in the app. Should I change it back?
Screenshot 2025-10-22 at 2 10 53 PM

url: actions/action_interface/
pre: bits-ai
parent: actions_heading
identifier: action_interface
weight: 10000
- name: Agents
url: actions/agents/
pre: robot-wui
identifier: agents
parent: actions_heading
weight: 20000
- name: Workflow Automation
url: actions/workflows/
pre: workflows
identifier: workflows
parent: actions_heading
weight: 10000
weight: 30000
- name: Build Workflows
url: actions/workflows/build/
parent: workflows
Expand Down Expand Up @@ -2835,7 +2847,7 @@ menu:
pre: app-builder
identifier: app_builder
parent: actions_heading
weight: 20000
weight: 40000
- name: Build Apps
url: actions/app_builder/build/
parent: app_builder
Expand Down Expand Up @@ -2891,24 +2903,18 @@ menu:
parent: app_builder
identifier: app_builder_saved_actions
weight: 10
- name: Action Interface
url: actions/action_interface/
pre: bits-ai
parent: actions_heading
identifier: action_interface
weight: 30000
- name: Datastore
url: actions/datastore/
pre: datastores-wui
parent: actions_heading
identifier: datastore
weight: 40000
weight: 50000
- name: Action Catalog
url: actions/actions_catalog/
pre: books
parent: actions_heading
identifier: action_catalog
weight: 50000
weight: 60000
- name: Connections
url: actions/connections/
parent: action_catalog
Expand Down
154 changes: 154 additions & 0 deletions content/en/actions/agents/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,154 @@
---
title: Agents
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The page doesn't include enough content to justify it's existence. Let's combine the two pages and add the "Build an agent" content to this page.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We also need to add a section that explains that you can invoke an agent via a Workflow step.

description: Build custom AI agents that can access the Action Catalog.
disable_toc: false
further_reading:
- link: "/actions/agents/build/"
tag: "Documentation"
text: "Create an agent"
- link: "/actions/actions_catalog/"
tag: "Documentation"
text: "Action Catalog"
- link: "https://www.datadoghq.com/knowledge-center/aiops/ai-agents/"
tag: "Knowledge Center"
text: "What are AI agents and how do they work?"
---

{{< callout url="https://app.datadoghq.com/actions/agents" btn_hidden="false" header="Join the Preview!" >}}
Agents is in Preview. Click <b>Request Access</b> and fill in the Datadog Product Preview Program form.
{{< /callout >}}

## Overview

You can build custom AI agents to act on your observability data and third-party integrations. Your agents can use any action from the [Action Catalog][7] to investigate problems, start remediation, or manage resources.

When building an agent, you can choose a template to get started. Templates come with pre-filled instructions and relevant tools. Templates are named after their main role, like Security Analyst, Log Analyzer, Incident Responder, or DevOps Assistant.

{{< img src="/actions/agents/blank-new-agent.png" alt="The Agents page, filtered to show only 'My agents'" style="width:100%;" >}}

## The Agents dashboard

You can create a new agent from the [Agents][1] page. The page lists information about existing agents, including the following:
- Agent Name
- Description
- Author
- Creation date

Hover over an agent for options to clone or delete it. You can also enable the **My agents** toggle to see only agents that you've created:

Check warning on line 37 in content/en/actions/agents/_index.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.pronouns

Avoid first-person pronouns such as 'My'.

{{< img src="/actions/agents/agent-dashboard.png" alt="The Agents page, filtered to show only 'My agents'" style="width:100%;" >}}

## Create an agent

Check warning on line 41 in content/en/actions/agents/_index.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.headings

'Create an agent' should use sentence-style capitalization.

### Build an agent from a blueprint

Blueprints are helpful starter agents that cover common use cases. They come loaded with instructions for the agent's behavior and helpful tools from the Action Catalog. Blueprints also showcase best practices for setting up agent functionality.

To build an agent from a blueprint:

1. Navigate to the [Agents][1] page.
1. In **Agent Blueprints**, click the blueprint you want to use.
1. Alternatively, you can click **New Agent** and browse the full list of blueprints.
1. Click **Create From Blueprint**.
1. Your new agent will have pre-populated settings and tools. You can immediately start chatting with the agent or [further customize it][2].

Check warning on line 53 in content/en/actions/agents/_index.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.tense

Avoid temporal words like 'will'.
1. Click the gear icon to close the agent's settings.

### Create a custom agent

Check warning on line 56 in content/en/actions/agents/_index.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.headings

'Create a custom agent' should use sentence-style capitalization.

To build an agent from scratch:

1. Navigate to the [Agents][1] page.
1. Click **New Agent**.
1. [Customize your agent][2]. Changes are saved automatically.
1. Start chatting with your agent.

## Customize your agent

Check warning on line 65 in content/en/actions/agents/_index.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.headings

'Customize your agent' should use sentence-style capitalization.

When configuring your agent, you have the following options for customization.

### Model

Click the dropdown menu to choose your GPT model. Current options include [GPT-4o][3], [GPT-4.1][4], and [GPT-5][5]. You can compare these models using [OpenAI's tool comparison tool][6].

### Instructions

Enter the instructions your agent will follow when performing tasks. You can describe the agent as if it were a person, including its role, specialties, and steps to follow. Click **Suggest With AI** to get help with writing and refining your instructions.

Check warning on line 75 in content/en/actions/agents/_index.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.tense

Avoid temporal words like 'will'.

Below is a sample set of instructions for an agent acting as an incident responder.

```
You are an Incident Responder AI assistant specialized in managing and coordinating incident response activities.

Your role involves:
- Guiding incident response procedures and best practices
- Helping assess incident severity and impact
- Coordinating communication between teams and stakeholders
- Managing incident lifecycle from detection to resolution
- Facilitating post-incident reviews and improvements

During incident response:
1. Help classify incident severity (P0/P1/P2/etc.)
2. Guide through incident response runbooks and procedures
3. Assist with stakeholder communication and updates
4. Track action items and follow-up tasks
5. Support post-mortem analysis and lessons learned

Focus on clear communication, structured processes, and continuous improvement of incident response capabilities.
```

### Tools

Click **+ Add Tool** to add actions from our [Action Catalog][7] for the agent to use. The agent is restricted to only its added tools. For example, if you encounter an error when the agent attempts to perform a task you've requested, it might be missing a necessary action.

Check warning on line 101 in content/en/actions/agents/_index.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.pronouns

Avoid first-person pronouns such as 'our'.

### MCP Servers

Check warning on line 103 in content/en/actions/agents/_index.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.headings

'MCP Servers' should use sentence-style capitalization.

Click the toggle button to enable [MCP (Model Context Protocol)][8]. MCP servers provide additional tools and capabilities that the agent can use to interact with external systems.

## Add an agent action

Check warning on line 107 in content/en/actions/agents/_index.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.headings

'Add an agent action' should use sentence-style capitalization.

After you create an agent, you can add it to a workflow or app.

### Add to a workflow

To invoke an agent in a workflow step:
1. In [Workflow Automation][9], navigate to a workflow and click **Edit**.
1. Click the plus **<i class="icon-plus-circled-wui"></i>** icon.
1. Select the **Execute Custom Agent** action.
1. Configure the action:
1. Enter a **Step name**.
1. Selection a **Connection**.
1. Select a **Custom Agent ID**.
1. Enter a **User Prompt**.
1. Optionally, add a [**Wait until condition**][11].
1. Optionally, add [**Retries**][12].
1. Click **Save**.

### Add to an app

To invoke an agent in an app:
1. In [App Builder][10], navigate to an app and click **Edit**.
1. Click the plus **<i class="icon-plus-2"></i>** icon, then click **Actions**.
1. Select the **Execute Custom Agent** action.
1. Configure the action:
1. Select the **Run Settings**.
1. Selection a **Connection**.
1. Select a **Custom Agent ID**.
1. Enter a **User Prompt**.
1. Click **Save**.

## Further Reading

{{< partial name="whats-next/whats-next.html" >}}

[1]: https://app.datadoghq.com/actions/agents
[2]: /actions/agents/build/#create-a-custom-agent
[3]: https://openai.com/index/hello-gpt-4o/
[4]: https://openai.com/index/gpt-4-1/
[5]: https://openai.com/gpt-5/
[6]: https://platform.openai.com/docs/models
[7]: /actions/actions_catalog/
[8]: /bits_ai/mcp_server
[9]: https://app.datadoghq.com/workflow
[10]: https://app.datadoghq.com/app-builder/apps/list
[11]: /actions/workflows/build/#wait-until-condition
[12]: /actions/workflows/build/#retries
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've never seen Datadog obfuscate names in screenshots. It makes the screenshot look unprofessional. Any content in the demo account should be fine to show to customers, including Datadog employee names.

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading