Datadog

Overview

Connect Datadog so AI clients can list monitors, inspect incidents, search events, and run short windowed metric queries - without pasting API keys into prompts.

This integration is read-first. Muting monitors or changing incidents is not exposed.

Prerequisites

• A Datadog account with permission to create API and application keys
• A stackgate.ai account
• The Datadog site for your organization (US1, US3, US5, EU, AP1, AP2, or Gov)

Getting credentials

1. Sign in to Datadog on the site that matches your organization (for EU use app.datadoghq.eu).
2. Open Organization Settings → API Keys and create or copy an API key. This identifies the organization.
3. Open Organization Settings → Application Keys and create an application key. This is user-scoped and required for read/management endpoints.
4. Grant the application key at least these scopes (names vary slightly by site):
   • monitors_read
   • events_read / events read
   • timeseries_query / metrics read
   • incident_read (needed for Incident Management tools)
5. In stackgate.ai, open My Integrations → Datadog.
6. Click Activate, paste the API key and application key, and select the site that matches your Datadog org. The wrong site returns 403 even with valid keys.
7. Save. stackgate.ai tests the API key (/api/v1/validate) and a read call with the application key before storing credentials.

See the Datadog API authentication docs and API and Application Keys.

Credentials reference

Using with AI clients

• Dedicated endpoint: POST /mcp/datadog with a Sanctum bearer token
• Private gateway: one config for all integrations - use datadog__* namespaced tools
• Business gateway: same namespaced tools when Datadog is enabled for the company

Key tools:

• list_monitors, get_monitor - find alerting monitors and inspect queries
• search_events - events in a required POSIX start/end window
• query_metrics - timeseries for a required from/to window (keep it to a few hours)
• list_incidents, get_incident - Incident Management status and commander context

After connecting, use Edit tool access to restrict tools (for example monitors only).

See Documentation for HTTP authentication and private gateway setup.

Test the integration

List Datadog monitors that are currently in Alert.
Show the last two hours of events tagged env:prod.
Query avg:system.cpu.user{*} for the last hour.
List open Datadog incidents.

Typical tools: list_monitors, search_events, query_metrics, list_incidents.

Troubleshooting

Datadog rate limits vary by endpoint and org plan (often hundreds to thousands of requests per hour). Prefer paginated list tools and short query windows.

Security and revocation

• Disconnect in My Integrations → Datadog to delete the stored keys from stackgate.ai.
• Revoke or rotate keys in Datadog Organization Settings → API Keys / Application Keys.
• Keys are stored encrypted. Tool calls are audit logged. Keys are never accepted as tool arguments.

Limitations

• Read-only MVP: no mute, downtime, or incident update tools.
• Metric and event tools require an explicit time window.
• Application keys are user-scoped; access follows that user's Datadog permissions.
• Gov and regional sites must be selected explicitly. There is no custom base URL field.