Skip to content

[MOPU-446] Add missing alerting MCP tools documentation #35941

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
manki23 merged 1 commit into from
Apr 13, 2026
Merged

[MOPU-446] Add missing alerting MCP tools documentation #35941

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
29 changes: 28 additions & 1 deletion content/en/bits_ai/mcp_server/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ Both metrics are tagged with `user_id`, `user_email`, and `client` (the MCP clie
The Datadog MCP Server supports _toolsets_, which allow you to use only the tools you need, saving valuable context window space. These toolsets are available:

- `core`: The default toolset for logs, metrics, traces, dashboards, monitors, incidents, hosts, services, events, and notebooks
- `alerting`: Tools for validating monitors, searching monitor groups, and retrieving monitor templates
- `alerting`: Tools for validating and creating monitors, searching monitor groups, retrieving monitor templates, analyzing monitor coverage, and searching SLOs
- `apm`: ([Preview][43]) Tools for in-depth [APM][28] trace analysis, span search, Watchdog insights, and performance investigation
- `cases`: Tools for [Case Management][38], including creating, searching, and updating cases; managing projects; and linking Jira issues
- `dashboards`: Tools for retrieving, creating, updating, and deleting [dashboards][44], plus widget schema reference and validation
Expand Down Expand Up @@ -375,6 +375,33 @@ Searches monitor groups by name or criteria.
- Show me all monitor groups in an alerting state.
- Find monitor groups related to the checkout service.

### `search_datadog_slos`
*Toolset: **alerting***\
*Permissions Required: `SLOs Read`*\
Searches Datadog SLOs by name, tags, or type. Supports query syntax for filtering by service, team, or other attributes.

- Search for SLOs related to `service:checkout`.
- List all SLOs tagged with `team:backend`.
- List SLOs for the payments service.

### `create_datadog_monitor`
*Toolset: **alerting***\
*Permissions Required: `Monitors Write`*\
Creates a Datadog monitor in draft mode. Monitors created with this tool do not send notifications and are set to priority 5 (low). Use `validate_datadog_monitor` to check the definition before creating and `get_datadog_monitor_templates` for query syntax examples. After creation, publish the monitor in the Datadog UI.

- Create a metric alert monitor for high CPU usage on the web service.
- Set up a log alert monitor for error spikes in the payments service.
- Create a monitor to track p95 latency for the checkout endpoint.

### `get_monitor_coverage`
*Toolset: **alerting***\
*Permissions Required: `Monitors Read`*\
Finds monitoring gaps and coverage for services or hosts. Returns which signals (such as error rate, latency, and request rate) are covered by existing monitors and which are missing. Use with `create_datadog_monitor` to fill gaps.

- Get monitoring coverage for `service:checkout`.
- What monitoring gaps exist for `host:web-01`?
- Find services that are missing error rate monitors.

<div class="alert alert-info">The <code>apm</code> toolset is in Preview. <a href="https://www.datadoghq.com/product-preview/apm-mcp-toolset/">Sign up for access.</a></div>

### `apm_search_spans`
Expand Down
Loading