DEVOPS
Vercel Build-Time Regression Detector to Datadog and Slack
Tracks Vercel build durations over time, flags when a deploy's build time regresses beyond a rolling-average threshold, emits a Datadog metric.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment-succeeded webhookVercel
- ActionAppend duration and compute rolling averagePostgres
- ActionSubmit build duration metric to DatadogDatadog
- LogicDetect regression vs rolling-average threshold
- OutputAlert platform channel in SlackSlack
What it does
Watches how long each Vercel build takes and catches slow-build regressions before they erode developer velocity. After every successful deploy it records the build duration, compares it to the recent rolling average, sends the value to Datadog as a custom metric, and pings Slack when a build is meaningfully slower than normal.
When to use it
Use it when build times are creeping up and you want a quantified, charted signal instead of anecdotes. Good for teams that already run Datadog dashboards and want build performance treated as a first-class operational metric.
How it works
- 1A Vercel deployment-succeeded webhook delivers the build duration and metadata.
- 2The flow appends the duration to a Postgres history table and computes the trailing rolling average.
- 3It submits the build duration as a custom metric to Datadog for dashboarding and long-term trends.
- 4A regression check fires when the new build exceeds the rolling average by the configured percentage.
- 5On regression it posts a Slack message naming the project, branch, duration, and percent over baseline so the team can investigate.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
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.
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…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.