> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Datadog

> Metrics, monitors, traces, and logs for investigations. Auto Monitors can create Datadog monitors.

**1. Create an application key**

In Datadog, go to **Organization Settings → Application Keys** and create a key. Give its role the scopes below.

**2. Connect**

Go to **Connections**, click **Connect** next to Datadog, choose your Datadog site (US1, US3, US5, EU, or AP1), and enter an API key and the application key.

## Permissions

The application key's role needs these scopes: `monitors_read`, `integrations_read`, `metrics_read`, `timeseries_query`, `logs_read_data`, `apm_read`, `apm_service_catalog_read`, `dashboards_read`, `events_read`, `slos_read`. Auto Monitors also needs `monitors_write`, `create_webhooks`, `manage_integrations`.

### Telemetry and monitor reads

Read logs, metrics, APM traces, dashboards and existing monitors.

| Scope | Used for |
| - | - |
| `monitors_read` | Monitors and alert state, and validating monitor definitions |
| `integrations_read` | Checking the webhook that delivers alerts to Ordyn (Auto Monitors) |
| `metrics_read` | Metric metadata |
| `timeseries_query` | Metric values |
| `logs_read_data` | Reading logs |
| `apm_read` | APM traces |
| `apm_service_catalog_read` | Service definitions, used to find your services and check access |
| `dashboards_read` | Dashboards |
| `events_read` | Charting event monitors (Auto Monitors) |
| `slos_read` | Charting SLO monitors (Auto Monitors) |

### Manage monitoring

Create and maintain the monitors Ordyn manages and the webhook that sends their alerts to Ordyn.

| Scope | Used for |
| - | - |
| `monitors_write` | Creating, updating and deleting the monitors Ordyn manages |
| `create_webhooks` | Creating the webhook that delivers alerts to Ordyn |
| `manage_integrations` | Repairing that webhook if it changes |

* Datadog checks permissions on the application key's role, not the API key. A missing scope shows up as `403 Forbidden` from the matching endpoint.

### How to grant

**Give the application key's role these scopes.** Open [https://app.datadoghq.com/organization-settings/application-keys](https://app.datadoghq.com/organization-settings/application-keys), select the application key Ordyn uses, and give its role these scopes: monitors\_read, monitors\_write, integrations\_read, create\_webhooks, manage\_integrations, metrics\_read, timeseries\_query, logs\_read\_data, apm\_read, apm\_service\_catalog\_read, dashboards\_read, events\_read, slos\_read.

Permission catalog version `2026-10-16.1`. See [permission changes](/reference/permission-changes).

A 403 on metric queries only, while logs work, usually means `timeseries_query` is missing.

## What Ordyn reads

Metrics, monitors and their history, APM traces by trace ID, logs, dashboards, and events such as deploys and config changes.

## What Ordyn writes

With Auto Monitors on, Ordyn creates and maintains its own monitors, plus one webhook that sends their alerts back to Ordyn.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.