Mute Monitor
Mute Monitor — see the properties below.
This node is also exposed as an AI Agent tool.
This node has 1 input port and 1 output port.
Common Properties
Every node shares these.
- Name — the node's display name on the canvas.
- Color — the node's colour on the canvas.
- Delay Before (sec) — wait this long before the node runs.
- Delay After (sec) — wait this long after the node runs.
- Continue On Error — carry on instead of failing the flow. Defaults to false.
info
When Continue On Error is true the error is not raised at all, so a Catch node will not see it either.
Inputs
| Property | Field | Description |
|---|---|---|
| Client ID | inClientID | Client ID from Connect node (optional if credentials provided) |
| Monitor ID | inMonitorID | ID of the monitor to mute |
Outputs
| Property | Field | Description |
|---|---|---|
| Success | outSuccess | Whether the mute operation was successful |
Options
| Property | Field | Description |
|---|---|---|
| Credentials | optCredentials | Datadog API keys |
| End (Unix Timestamp) | optEnd | Unix timestamp when mute should end (indefinite if not set) |
| Scope | optScope | Scope to mute (e.g. host:myhost، env:prod) |
| Site | optSite | Datadog site (defaults to datadoghq.com) |
Requirements
- A Client ID from this package's Connect node, unless you set credentials directly on this node.
- Datadog API Keys — API Key and Application Key for Datadog authentication
value— API Key (password, required). Your Datadog API keyapplication_key— Application Key (password, optional). Required for query and management operations (monitors, logs, downtimes)
Store these in a Vault and reference the vault item from the node, rather than typing the secret into the property.
Related nodes
Create Monitor · Get Monitor · List Monitors
Elsewhere in the package: Connect · Disconnect · Submit Metrics · Query Timeseries · Create Event · Query Logs · Send Logs · Create Downtime · List Downtimes · Cancel Downtime and 1 more
See also
- Datadog — every node in this package
- Message object — how properties read values from
msg - Handling failure — Continue On Error, Catch and retries