Datadog

Read and manage Datadog monitors, events, incidents, downtimes, SLOs, service catalogue, hosts, logs and metric queries.

Route observability signals into service desks, status pages and on-call workflows, and keep monitors and downtimes in step with change calendars.

Build a flow with Datadog Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

catalog entities

List catalog entities
Source
Software Catalog entities (services, datastores, queues, systems, APIs) with owners.

downtimes

Schedule downtime
Destination
Not retried automatically
Schedules a one-time or recurring downtime for one monitor or monitors with given tags.
Get downtime
Source
One downtime with its schedule and status.
List downtimes
Source
Scheduled, active and past downtimes with their monitor selection and schedule.
Update downtime
Destination
Duplicate protected
Changes the scope, monitor selection, schedule or message of a downtime.

events

Post event
Destination
Not retried automatically
Posts an event (for example a deploy or change record) to the event stream.
Get event
Source
One event with its full attributes.
List events
Source
Events from the Events Explorer matching a search query and time range.
Search events
Source
Event search with a request body, for long queries and time zone options.

hosts

List hosts
Source
Infrastructure hosts with aliases, apps, tags by source and agent metadata.

incidents

Declare incident
Destination
Not retried automatically
Declares an incident with severity, state, customer impact and commander.
Get incident
Source
One incident with fields, impact and commander.
List incidents
Source
Incidents with severity, state, impact and timing fields.
Search incidents
Source
Incident search with Datadog's incident query syntax, for example state:active.
Update incident
Destination
Duplicate protected
Updates title, severity, state, impact, timings or commander of an incident.

logs

Search logs
Source
Indexed log events matching a query within a bounded time window.

metric metadata

Get metric metadata
Source
Type, unit, description and integration of a metric.

metrics

Query metrics
Source
Timeseries points for a metric query over a bounded time window.

monitors

Create monitor
Destination
Not retried automatically
Creates a monitor with a query, message, tags, priority and options.
Get monitor
Source
One monitor with its options, state and optional matching downtimes.
List monitors
Source
Monitors with their query, options, tags and overall state.
Search monitors
Source
Monitor search with Datadog's monitor query syntax, including status filters.
Update monitor
Destination
Duplicate protected
Edits a monitor. Omitted fields are unchanged; options are replaced as a whole.

services

Get service definition
Source
One service definition by service name.
List service definitions
Source
Service definitions from the Software Catalog with owner, tier and contacts.

slo history

Get SLO history
Source
SLI value, uptime and remaining error budget for an SLO over a time window.

slos

Get SLO
Source
One SLO with its thresholds and configured alert IDs.
List SLOs
Source
Service level objectives with targets, timeframes and source monitors or queries.

Authentication

API key and application key

Plans and access

All Datadog plans; incidents, the software catalogue and logs require the corresponding products. Application keys inherit the creating user's permissions and can be scoped (monitors_read, monitors_write, monitors_downtime, incident_read, incident_write, events_read, logs_read_data, slos_read, apm_service_catalog_read, metrics_read, hosts_read).

Test environment

A 14-day free trial organisation works for testing.

Rate limits

Per-organisation, per-endpoint limits reported in X-RateLimit-Limit/Remaining/Reset headers; HTTP 429 when exceeded (for example 300 monitor reads per minute, logs search 300 per hour by default).

Provider events

Webhooks integration for monitor, incident and event notifications. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

The Incidents v2 API is in preview (unstable) at Datadog; its fields can change.
Incident notification handles are not exposed, so creating or updating an incident does not page anyone through Nexra; monitor messages can still contain @-handles.
Deleting monitors, cancelling downtimes and deleting incidents are not implemented.
Events are posted with the v1 events endpoint on the API host; the v2 event-management intake host is not used.
Log search is limited to 30-day windows and metric queries to 31-day windows per call.
Monitor, incident, event and downtime creates have no idempotency key; uncertain writes are not repeated automatically.