DEVOPS
Post-Pipeline Runner-Tier Right-Sizing Advisor
On each completed GitLab pipeline, correlates job CPU/memory utilization from Datadog against the runner tier used and alerts Slack when a job is over- or under-provisioned.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab pipeline-completed webhookGitLab
- ActionQuery Datadog for per-job CPU/memory utilizationDatadog
- LogicClassify jobs as over/under/right-sized vs tier
- LogicSuppress fully right-sized pipelines
- OutputAlert Slack with tier change and savingsSlack
What it does
After every pipeline finishes, it cross-references actual runner resource utilization (from Datadog) with the runner tier each job requested, then recommends right-sizing — flagging both wasteful over-provisioning and throttled under-provisioning.
When to use it
When you pay for large runner tiers but suspect most jobs barely use them, or when slow jobs are silently starved for CPU. Best for teams running self-hosted or tier-priced GitLab runners.
How it works
- 1A GitLab webhook triggers when a pipeline completes.
- 2The flow queries Datadog for per-job CPU and memory utilization metrics during the pipeline window.
- 3A logic step compares peak utilization against the requested runner tier, classifying each job as over-provisioned, right-sized, or throttled.
- 4A filter step suppresses pipelines where every job is already right-sized.
- 5For mismatched jobs, an alert with the recommended tier change and projected savings is posted to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.