DATA OPS
Datadog Pipeline SLA Incident Triage
Triggers on a Datadog data-pipeline SLA monitor alert, enriches it with recent run context.
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog SLA monitor alertDatadog
- ActionFetch metric series and recent eventsDatadog
- LogicAgent drafts triage summary
- OutputPost triage note to Microsoft TeamsMicrosoft Teams
- ActionAppend incident entry to Confluence runbookConfluence
What it does
Turns a raw Datadog pipeline-SLA alert into an actionable triage note. When a monitor for end-to-end pipeline latency or job duration fires, the flow gathers the alerting metric and recent events, then an agent writes a plain-language summary of what breached, the likely blast radius, and the first thing to check. The note goes to the data on-call Teams channel and is appended to the pipeline's Confluence runbook for the incident record.
When to use it
When Datadog alerts on pipeline SLAs are too terse to act on and on-call spends the first ten minutes just figuring out what the alert means. Use it to ship a ready-to-act triage summary the moment the monitor fires.
How it works
- 1A Datadog monitor alert webhook triggers the flow.
- 2The flow fetches the alerting metric series and recent related events from Datadog.
- 3An agent step composes a triage summary: what breached, affected downstream tables, and suggested first checks.
- 4The summary posts to the data on-call channel in Microsoft Teams.
- 5The same note is appended to the pipeline's Confluence runbook page as a timestamped incident entry.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.