Skip to content
Recued
Menu
← Back to recipes

Mute a Datadog monitor scope

by recued-core v1

Approval-gated Datadog monitor scoped mute workflow. It reads the target monitor for context, then mutes exactly one monitor scope through recued-core.datadog until a required POSIX end timestamp. It does not mute all monitors, create downtimes, update monitor configuration, delete monitors, or call arbitrary Datadog APIs.

How it works 6 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (6 steps)
scope trim
Trim whitespace from setting scope
has_scope compare
Check if scope has data
monitor ?
mute ?
skip: step.has_scope not_equal true
skipped compare
Check if has scope does not equal true
card to_summary
Format results as a summary card
Settings 4 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

scope setting =
datadog setting =
monitor id setting = 0
end timestamp setting = 0

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Datadog connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

datadog datadogmonitormutemaintenanceapprovalincident-responsepack:datadog

Details

6 steps 4 configurable settings recipe_id: mute-datadog-monitor