DEVOPS
GitLab CI Cost-Spike Real-Time Alert
Monitors hourly GitLab runner-minute consumption and, when spend spikes well above the rolling baseline, pages on-call via PagerDuty with the offending project, pipeline…
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule
- ActionFetch last hour of runner minutes by projectGitLab
- LogicCompare against 7-day rolling baseline
- LogicExit if no project breaches threshold
- OutputTrigger PagerDuty incident with attributionPagerDuty
What it does
Watches CI runner consumption in near real time and catches cost anomalies — a runaway loop, an accidentally un-cached build, a misconfigured matrix job — before they burn through a month's budget in a day.
When to use it
When a single bad commit or pipeline misconfiguration can quietly torch your runner budget and you want to catch it within the hour rather than on the invoice. Best for teams with budget guardrails or chargeback.
How it works
- 1An hourly scheduled trigger fires.
- 2The flow fetches the last hour of runner-minute usage by project from the GitLab API.
- 3A logic step compares it against a 7-day rolling hourly baseline and flags any project exceeding the spike threshold.
- 4A filter step exits quietly when no project breaches the threshold.
- 5For a breach, the flow attributes the spike to the top-consuming pipeline and triggers a PagerDuty incident with the project, pipeline, and probable cause.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.