This guide walks you through connecting Datadog to Clarion. Once connected, AI agents can pull observability context from Datadog while they triage — searching logs, APM spans, events, and the service catalog — and manage Datadog cases to track their findings alongside your team.
Estimated time: 5-10 minutes. You will need permission to create API and Application keys in your Datadog organization, plus access to the Clarion workspace where you want to connect Datadog.
| What | Purpose |
|---|
| Datadog site | The region your organization runs in (e.g. US1, EU1). Clarion uses it to reach the correct Datadog API and dashboard. |
| API key | Identifies your Datadog organization on every request. |
| Application key | Authorizes the specific actions agents can take. The scopes you grant it determine which tools work — see Step 3. |
Clarion talks to Datadog through Datadog’s official Bits AI MCP server. Your keys are stored encrypted and injected server-side when an agent calls a Datadog tool — they are never exposed to the agent’s sandbox or written into transcripts. Prerequisites
- A Datadog account on a supported site
- Permission to create API keys and Application keys (Organization Settings)
- Datadog’s MCP server (Bits AI) available for your organization — see Datadog’s setup docs
- A Clarion workspace with the Datadog integration page open
Step 1 — Choose your Datadog site
Clarion supports the regions where Datadog publishes its MCP server:
| Site | Value |
|---|
| US1 | datadoghq.com |
| US3 | us3.datadoghq.com |
| US5 | us5.datadoghq.com |
| EU1 | datadoghq.eu |
| AP1 | ap1.datadoghq.com |
| AP2 | ap2.datadoghq.com |
Step 2 — Create an API key
- In Datadog, go to Organization Settings → API Keys.
- Click New Key, give it a name (e.g.
Clarion), and create it.
- Copy the key value.
Step 3 — Create an Application key
The Application key’s scopes decide which tools agents can use. Create it with the full set below so every Datadog tool works; grant a subset if you only want certain capabilities.
- In Datadog, go to Organization Settings → Application Keys.
- Click New Key, name it (e.g.
Clarion), and add these scopes:
| Scope | Unlocks |
|---|
mcp_read | Base scope required for all Datadog tools |
logs_read_data, logs_read_index_data | Log Search |
apm_read | APM Span Search |
apm_service_catalog_read | Service Catalog & Service Dependencies |
cases_read | Case search and read (cases and projects) |
cases_write | Create / update cases, add comments, link Jira |
user_access_read | User Search (resolving case assignees) |
- Copy the key value.
If an Application key is missing a scope, the matching tools fail at call time rather than at setup. If a tool returns a permissions error during triage, re-check the key’s scopes here.
Step 4 — Connect Datadog in Clarion
- In Clarion, open Integrations and find Datadog.
- Select your Datadog site from Step 1.
- Paste your API Key (Step 2) and Application Key (Step 3).
- Click Save.
To rotate keys later, return to this page and enter new values. To remove the integration entirely, see Disconnect.
What agents can do
Once connected, agents on this workspace can use the Datadog tools below. Add the ones you want to a skill the agent runs (for example, an enrichment skill that gathers observability context, or a triage skill that opens a case for confirmed issues).
Observability (read-only)
| Tool | What it does |
|---|
| Log Search | Search logs by service and time range |
| APM Span Search | Search APM spans — request URLs, headers, and body tags |
| Event Search | Search deployments, monitor alerts, and infrastructure changes |
| Service Catalog | List services with their runtime and topology |
| Service Dependencies | Map upstream and downstream service dependencies |
Case Management
| Tool | Type | What it does |
|---|
| Case Search | Read | Find cases by status, priority, project, or assignee |
| Case Details | Read | Full case, including timeline and custom attributes |
| Case Projects / Project Details | Read | List and inspect the projects cases live in |
| User Search | Read | Resolve a Datadog user to assign a case to |
| Create Case | Write | Open a case to track an investigation |
| Update Case | Write | Change status, priority, assignee, or other fields |
| Add Case Comment | Write | Post a markdown comment to a case’s timeline |
| Link Jira to Case | Write | Link a Jira issue to a case for cross-platform tracking |
The case write tools (Create, Update, Add Comment, Link Jira) require approval by default — the agent pauses and waits for a human before it changes anything in your Datadog workspace. You can adjust this per tool or per action under Workspace → Tools. Link Jira to Case also requires a Jira integration configured on the Datadog side.
Disconnect
To remove the integration:
- In Clarion, open Integrations → Datadog.
- Click Disconnect.
This deletes the stored API and Application keys. Agents on this workspace will no longer see the Datadog tools, and any saved skills that reference them will surface the integration as missing until you reconnect.
Troubleshooting
The Application key is missing the scope that tool needs. Re-create the key in Organization Settings → Application Keys with the full scope set from Step 3, then re-save it in Clarion.
The case tools need cases_read and cases_write (and user_access_read for assignee lookup). Confirm those scopes are on the Application key, and that the case tools are added to the skill the agent is running.
”Unknown Datadog site” or no data returned
The selected site doesn’t match your organization’s region. Check the URL you use to reach Datadog and pick the matching site in Step 1. US1-FED and US2-FED are not supported.
Confirm Datadog’s MCP server (Bits AI) is available for your organization — see Datadog’s setup docs — and that the integration shows as connected in Clarion.
Forwarding Datadog monitor alerts into Clarion as alerts is coming soon. Today the Datadog integration powers the agent tools described above.
