Skip to main content

Documentation Index

Fetch the complete documentation index at: https://onecli.sh/docs/llms.txt

Use this file to discover all available pages before exploring further.

Datadog is available on the Cloud plan only.

​
Overview

OneCLI connects AI agents to Datadog using an API key and application key. Agents can query metrics, list monitors, check incident status, and view dashboard data. The gateway injects both keys into requests to the Datadog API automatically. This is useful for on-call agents that need to investigate incidents, coding agents that check deployment metrics, or reporting agents that pull monitoring data.

​
Setup

1

Create API and application keys in Datadog

In the Datadog console, go to Organization Settings > API Keys and create a new API key. Then go to Application Keys and create a new application key. Copy both values.
2

Connect in OneCLI

Open the OneCLI dashboard, go to Connections > Datadog, and paste:
  • API Key: your Datadog API key
  • Application Key: your Datadog application key
  • Site: your Datadog site (e.g., datadoghq.com, datadoghq.eu)

​
What agents can do

  • Query time-series metrics with custom queries and time ranges
  • List monitors and their current statuses (OK, Alert, Warn, No Data)
  • Get details for a specific monitor, including recent state changes
  • List active incidents and their severity, timeline, and postmortem status
  • Query dashboard widget data
  • Search and read log entries
  • List hosts and their tags
  • Query infrastructure metrics (CPU, memory, disk, network)
  • Check SLO (Service Level Objective) status and error budgets
  • Read and create events

​
Controlling access with rules

Use OneCLI’s rules engine to limit what agents can do with Datadog. For example, you can restrict agents to read-only access so they can query metrics and monitors but cannot modify alert configurations, or limit queries to specific time ranges. Rules are evaluated before credential injection, so a blocked request never reaches Datadog.