Skip to main content
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.

​
Manage monitoring

Create and maintain the monitors Ordyn manages and the webhook that sends their alerts to Ordyn.
  • 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, 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. 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.