Datadog

Work with Datadog from chat - inspect monitors, metrics, logs, incidents, dashboards, and observability data.

Powered by ClawLink, an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Datadog API access yourself.

Setup in 3 Steps

Step 1: Install	Step 2: Pair Account	Step 3: Connect Datadog
		App-specific connection GIF coming soon
Run the install command in OpenClaw	Sign in and approve the device	Open the dashboard and connect Datadog

Connection flow

User → ClawLink OAuth → Datadog account
         ↓
    OpenClaw tools
    (via ClawLink)

Step 1 — Install the ClawLink plugin:

openclaw plugins install clawhub:clawlink-plugin

Start a fresh chat after installing.

Step 2 — Pair ClawLink:

1. Call clawlink_begin_pairing
2. Open the returned URL in your browser
3. Sign in to ClawLink and approve the device

Step 3 — Connect Datadog: Open claw-link.dev/dashboard?add=datadog, complete the OAuth flow, then confirm.

App-specific connection GIF coming soon

Step 4 — Verify and discover:

// 1. Verify Datadog is connected
clawlink_list_integrations()

// 2. List available tools
clawlink_list_tools({ integration: "datadog" })

// 3. Search tools if needed
clawlink_search_tools({ query: "monitor", integration: "datadog" })

Architecture

┌─────────────────────────────────────────────────────────┐
│                    OpenClaw (you)                       │
├─────────────────────────────────────────────────────────┤
│  ClawLink Plugin  →  clawlink_* tools                   │
├─────────────────────────────────────────────────────────┤
│                    ClawLink Cloud                       │
│         (credentials, connection state, routing)        │
├─────────────────────────────────────────────────────────┤
│              Datadog API (user's account)               │
└─────────────────────────────────────────────────────────┘

Tool reference

Read operations

Write operations

Code examples

Example 1: List all monitors and find critical ones

// Get all monitors
const monitors = await clawlink_call_tool({
  tool: "clawlink_list_tools",
  parameters: { integration: "datadog" }
});

// Then get details for a specific monitor
const monitor = await clawlink_call_tool({
  tool: "datadog_get_monitor",
  parameters: { monitor_id: "123456" }
});

// Or list all monitors with details
const allMonitors = await clawlink_call_tool({
  tool: "datadog_list_monitors",
  parameters: {}
});

Example 2: Query metrics and search logs

// List available metrics first
const metrics = await clawlink_call_tool({
  tool: "datadog_list_metrics",
  parameters: { from: 1704067200 }
});

// Query specific metrics
const timeseries = await clawlink_call_tool({
  tool: "datadog_query_metrics",
  parameters: {
    query: "system.cpu.user{*}",
    from: 1704067200,
    to: 1704153600
  }
});

// Search logs for errors
const errors = await clawlink_call_tool({
  tool: "datadog_search_logs",
  parameters: {
    query: "status:error",
    from: 1704067200000,
    to: 1704153600000
  }
});

Example 3: Create and manage monitors

// Create a monitor
const newMonitor = await clawlink_call_tool({
  tool: "datadog_create_monitor",
  parameters: {
    name: "High CPU Alert",
    type: "metric alert",
    query: "avg(last_5m):system.cpu.user{*} > 90",
    message: "CPU usage is above 90%"
  }
});

// Mute a monitor during maintenance
await clawlink_call_tool({
  tool: "datadog_mute_monitor",
  parameters: {
    monitor_id: "123456",
    scope: "env:production"
  }
});

Example 4: Investigate an incident

// List recent incidents
const incidents = await clawlink_call_tool({
  tool: "datadog_list_incidents",
  parameters: {}
});

// Get service dependencies for the affected service
const deps = await clawlink_call_tool({
  tool: "datadog_get_service_dependencies",
  parameters: { service_name: "payment-service" }
});

// Search traces for errors
const traces = await clawlink_call_tool({
  tool: "datadog_search_traces",
  parameters: { service: "payment-service", status: "error" }
});

Error handling

Security & Permissions

• ClawLink stores only the OAuth token, never the raw API key
• Device credentials are stored locally in OpenClaw plugin config
• datadog_list_api_keys returns metadata only (no secret key values)
• Datadog OAuth scopes are determined by ClawLink's registered app — user may need to reconnect if scopes change

Troubleshooting

Tools not showing up after install:

• Start a fresh OpenClaw chat to reload the plugin catalog
• Call clawlink_list_integrations to confirm ClawLink is paired

"Integration not connected" error:

• Direct user to claw-link.dev/dashboard?add=datadog
• Confirm they complete the OAuth flow and approve the connection

Empty results from datadog_list_events:

• Events are often sparse — start with a broad time range and minimal filters
• Combining multiple filters (tags + sources + priority) with narrow ranges may return empty results

Powered by ClawLink — your OpenClaw integration hub for Datadog.