Datadog

Usage Instructions

Integrate Datadog monitoring into workflows. Submit metrics, manage monitors, query logs, create events, handle downtimes, and more.

Tools

`datadog_submit_metrics`

Submit custom metrics to Datadog. Use for tracking application performance, business metrics, or custom monitoring data.

Input

Parameter	Type	Required	Description
`series`	string	Yes	JSON array of metric series to submit. Each series should include metric name, type (gauge/rate/count), points (timestamp/value pairs), and optional tags.
`apiKey`	string	Yes	No description
`site`	string	No	No description

Output

Parameter	Type	Description
`success`	boolean	Whether the metrics were submitted successfully
`errors`	array	Any errors that occurred during submission

`datadog_query_timeseries`

Query metric timeseries data from Datadog. Use for analyzing trends, creating reports, or retrieving metric values.

Input

Parameter	Type	Required	Description
`query`	string	Yes	Datadog metrics query (e.g., "avg:system.cpu.user{*}", "sum:nginx.requests{env:prod}.as_count()")
`from`	number	Yes	No description
`to`	number	Yes	No description
`apiKey`	string	Yes	No description
`applicationKey`	string	Yes	No description
`site`	string	No	No description

Output

Parameter	Type	Description
`series`	array	Array of timeseries data with metric name, tags, and data points
`status`	string	Query status

`datadog_create_event`

Post an event to the Datadog event stream. Use for deployment notifications, alerts, or any significant occurrences.

Input

Parameter	Type	Required	Description
`title`	string	Yes	No description
`text`	string	Yes	No description
`alertType`	string	No	Alert type: error, warning, info, success, user_update, recommendation, or snapshot
`priority`	string	No	No description
`host`	string	No	Host name to associate with this event (e.g., "web-server-01", "prod-api-1")
`tags`	string	No	Comma-separated list of tags (e.g., "env:production,service:api", "team:backend,priority:high")
`aggregationKey`	string	No	No description
`sourceTypeName`	string	No	No description
`dateHappened`	number	No	Unix timestamp in seconds when the event occurred (e.g., 1705320000, defaults to now)
`apiKey`	string	Yes	No description
`site`	string	No	No description

Output

Parameter	Type	Description
`event`	object	The created event details
↳ `id`	number	Event ID
↳ `title`	string	Event title
↳ `text`	string	Event text
↳ `date_happened`	number	Unix timestamp when event occurred
↳ `priority`	string	Event priority
↳ `alert_type`	string	Alert type
↳ `host`	string	Associated host
↳ `tags`	array	Event tags
↳ `url`	string	URL to view the event in Datadog

`datadog_create_monitor`

Create a new monitor/alert in Datadog. Monitors can track metrics, service checks, events, and more.

Input

Parameter	Type	Required	Description
`name`	string	Yes	No description
`type`	string	Yes	Monitor type: metric alert, service check, event alert, process alert, log alert, query alert, composite, synthetics alert, slo alert
`query`	string	Yes	Monitor query (e.g., "avg(last_5m):avg:system.cpu.idle{*} < 20", "logs("status:error").index("main").rollup("count").last("5m") > 100")
`message`	string	No	No description
`tags`	string	No	No description
`priority`	number	No	No description
`options`	string	No	JSON string of monitor options (thresholds, notify_no_data, renotify_interval, etc.)
`apiKey`	string	Yes	No description
`applicationKey`	string	Yes	No description
`site`	string	No	No description

Output

Parameter	Type	Description
`monitor`	object	The created monitor details
↳ `id`	number	Monitor ID
↳ `name`	string	Monitor name
↳ `type`	string	Monitor type
↳ `query`	string	Monitor query
↳ `message`	string	Notification message
↳ `tags`	array	Monitor tags
↳ `priority`	number	Monitor priority
↳ `overall_state`	string	Current monitor state
↳ `created`	string	Creation timestamp
↳ `modified`	string	Last modification timestamp

`datadog_get_monitor`

Input

Parameter	Type	Required	Description
`monitorId`	string	Yes	The ID of the monitor to retrieve (e.g., "12345678")
`groupStates`	string	No	Comma-separated group states to include (e.g., "alert,warn", "alert,warn,no data,ok")
`withDowntimes`	boolean	No	No description
`apiKey`	string	Yes	No description
`applicationKey`	string	Yes	No description
`site`	string	No	No description

Output

Parameter	Type	Description
`monitor`	object	The monitor details
↳ `id`	number	Monitor ID
↳ `name`	string	Monitor name
↳ `type`	string	Monitor type
↳ `query`	string	Monitor query
↳ `message`	string	Notification message
↳ `tags`	array	Monitor tags
↳ `priority`	number	Monitor priority
↳ `overall_state`	string	Current monitor state
↳ `created`	string	Creation timestamp
↳ `modified`	string	Last modification timestamp

`datadog_list_monitors`

Input

Parameter	Type	Required	Description
`groupStates`	string	No	Comma-separated group states to filter by (e.g., "alert,warn", "alert,warn,no data,ok")
`name`	string	No	Filter monitors by name with partial match (e.g., "CPU", "Production")
`tags`	string	No	Comma-separated list of tags to filter by (e.g., "env:prod,team:backend")
`monitorTags`	string	No	Comma-separated list of monitor tags to filter by (e.g., "service:api,priority:high")
`withDowntimes`	boolean	No	No description
`page`	number	No	No description
`pageSize`	number	No	No description
`apiKey`	string	Yes	No description
`applicationKey`	string	Yes	No description
`site`	string	No	No description

Output

Parameter	Type	Description
`monitors`	array	List of monitors
↳ `id`	number	Monitor ID
↳ `name`	string	Monitor name
↳ `type`	string	Monitor type
↳ `query`	string	Monitor query
↳ `overall_state`	string	Current state
↳ `tags`	array	Tags

`datadog_mute_monitor`

Input

Parameter	Type	Required	Description
`monitorId`	string	Yes	The ID of the monitor to mute (e.g., "12345678")
`scope`	string	No	Scope to mute (e.g., "host:myhost", "env:prod"). If not specified, mutes all scopes.
`end`	number	No	Unix timestamp in seconds when the mute should end (e.g., 1705323600). If not specified, mutes indefinitely.
`apiKey`	string	Yes	No description
`applicationKey`	string	Yes	No description
`site`	string	No	No description

Output

Parameter	Type	Description
`success`	boolean	Whether the monitor was successfully muted

`datadog_query_logs`

Search and retrieve logs from Datadog. Use for troubleshooting, analysis, or monitoring.

Input

Parameter	Type	Required	Description
`query`	string	Yes	Log search query using Datadog query syntax (e.g., "service:web-app status:error", "host:prod-* @http.status_code:500")
`from`	string	Yes	Start time in ISO-8601 format or relative time (e.g., "now-1h", "now-15m", "2024-01-15T10:00:00Z")
`to`	string	Yes	End time in ISO-8601 format or relative time (e.g., "now", "now-5m", "2024-01-15T12:00:00Z")
`limit`	number	No	No description
`sort`	string	No	Sort order: "timestamp" for oldest first, "-timestamp" for newest first
`indexes`	string	No	No description
`apiKey`	string	Yes	No description
`applicationKey`	string	Yes	No description
`site`	string	No	No description

Output

Parameter	Type	Description
`logs`	array	List of log entries
↳ `id`	string	Log ID
↳ `content`	object	Log content
↳ `timestamp`	string	Log timestamp
↳ `host`	string	Host name
↳ `service`	string	Service name
↳ `message`	string	Log message
↳ `status`	string	Log status/level
`nextLogId`	string	Cursor for pagination

`datadog_send_logs`

Input

Parameter	Type	Required	Description
`logs`	string	Yes	JSON array of log entries. Each entry should have message and optionally ddsource, ddtags, hostname, service.
`apiKey`	string	Yes	No description
`site`	string	No	No description

Output

Parameter	Type	Description
`success`	boolean	Whether the logs were sent successfully

`datadog_create_downtime`

Input

Parameter	Type	Required	Description
`scope`	string	Yes	Scope to apply downtime to (e.g., "host:myhost", "env:production", or "*" for all)
`message`	string	No	No description
`start`	number	No	Unix timestamp for downtime start in seconds (e.g., 1705320000, defaults to now)
`end`	number	No	No description
`timezone`	string	No	Timezone for the downtime (e.g., "America/New_York", "UTC", "Europe/London")
`monitorId`	string	No	Specific monitor ID to mute (e.g., "12345678")
`monitorTags`	string	No	Comma-separated monitor tags to match (e.g., "team:backend,priority:high")
`muteFirstRecoveryNotification`	boolean	No	No description
`apiKey`	string	Yes	No description
`applicationKey`	string	Yes	No description
`site`	string	No	No description

Output

Parameter	Type	Description
`downtime`	object	The created downtime details
↳ `id`	number	Downtime ID
↳ `scope`	array	Downtime scope
↳ `message`	string	Downtime message
↳ `start`	number	Start time (Unix timestamp)
↳ `end`	number	End time (Unix timestamp)
↳ `active`	boolean	Whether downtime is currently active

`datadog_list_downtimes`

Input

Parameter	Type	Required	Description
`currentOnly`	boolean	No	No description
`monitorId`	string	No	Filter by monitor ID (e.g., "12345678")
`apiKey`	string	Yes	No description
`applicationKey`	string	Yes	No description
`site`	string	No	No description

Output

Parameter	Type	Description
`downtimes`	array	List of downtimes
↳ `id`	number	Downtime ID
↳ `scope`	array	Downtime scope
↳ `message`	string	Downtime message
↳ `start`	number	Start time (Unix timestamp)
↳ `end`	number	End time (Unix timestamp)
↳ `active`	boolean	Whether downtime is currently active

`datadog_cancel_downtime`

Input

Parameter	Type	Required	Description
`downtimeId`	string	Yes	The ID of the downtime to cancel (e.g., "abc123def456")
`apiKey`	string	Yes	No description
`applicationKey`	string	Yes	No description
`site`	string	No	No description

Output

Parameter	Type	Description
`success`	boolean	Whether the downtime was successfully canceled

Datadog

On this page