DEVOPS
Datadog Infra-Change Event to Auto-Filed Linear Drift Ticket
Triggers on a Datadog event signaling an out-of-band infrastructure change, confirms the resource drifted from Terraform state.
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog infra-change eventDatadog
- ActionExtract affected resource from payloadDatadog
- ActionTargeted terraform plan to confirm driftShell
- LogicEnd if state still matches
- OutputFile owner-assigned Linear ticketLinear
What it does
When Datadog emits an infrastructure-change event (a security group edited in console, an instance type swapped, a tag stripped), this workflow cross-checks the affected resource against committed Terraform state, and if it truly drifted, files a Linear issue with the diff and a suggested reconciliation path, assigned to the resource's owning team.
When to use it
Use it when Datadog already captures cloud change events and you want every confirmed drift to become a tracked, owned work item instead of a forgotten alert. Ideal for teams that reconcile drift in sprints rather than reverting on sight.
How it works
- 1A Datadog event trigger fires on the infrastructure-change monitor.
- 2An action pulls the affected resource address from the event payload.
- 3A shell action runs a targeted `terraform plan` on that resource to confirm real drift.
- 4A logic step ends the run if state still matches (event was a no-op or already reconciled).
- 5An action resolves the owning team from resource tags.
- 6An output step creates a Linear ticket with the diff, owner assignment, and reconcile-or-import guidance.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect LinearIssues, projects, cycles, triage.
- 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 DevOps workflows
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
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.