IT OPS

Reconcile Orphaned Datadog Downtimes Against the Outlook Calendar

On a schedule, this workflow compares active Datadog downtimes to the Outlook maintenance calendar and clears any downtime whose window has already ended.

CategoryIT Ops
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily reconciliation schedule
  • ActionList active Datadog downtimesDatadogDatadog
  • ActionFetch current Outlook maintenance eventsOutlook
  • LogicClassify each downtime: active, expired, orphaned
  • ActionCancel expired downtimes in DatadogDatadogDatadog
  • OutputSend reconciliation digest to SlackSlack

What it does

Finds downtimes that should have been lifted. It lists every active Datadog downtime, matches each against the Outlook maintenance calendar, cancels downtimes whose windows have ended, and flags any downtime with no matching calendar event at all.

When to use it

Use it as a safety net when a window-end automation fails or someone mutes monitors manually and forgets to undo it — a common cause of missed production alerts.

How it works

  1. 1A daily schedule fires the reconciler.
  2. 2It fetches all active Datadog downtimes and the current Outlook maintenance events.
  3. 3For each downtime, a matcher classifies it: still inside its window, expired window, or no matching event.
  4. 4Expired downtimes are cancelled in Datadog so monitors resume alerting.
  5. 5Orphaned downtimes (no calendar backing) are left in place but flagged.
  6. 6A Slack digest summarizes what was cleared and lists the orphans for an engineer to confirm or remove.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DatadogMetrics, traces, log search.
  2. 2
    Connect OutlookMail, calendar, contacts.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.