DEVOPS
Cloudflare Cache Hit-Ratio Regression Sentinel with Auto-Rollback MR
Watches Cloudflare cache hit ratio on a schedule, and when a recent config change tanks efficiency it correlates the drop to the offending commit and opens a GitLab rollback…
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 15 minutes
- ActionPull cache hit ratio vs baseline (Cloudflare GraphQL)Cloudflare
- LogicDrop exceeds threshold?
- ActionFind latest merged edge-config commitGitLab
- ActionOpen revert merge requestGitLab
- OutputPost MR + before/after ratio to on-call channelSlack
What it does
This sentinel runs every 15 minutes, pulls the zone-level cache hit ratio from the Cloudflare GraphQL Analytics API, and compares it to the trailing 24-hour baseline. When the ratio drops past your threshold (default 8 points), it identifies the most recent merged change to your edge config repo, reverts that commit, and opens a GitLab merge request so an operator can ship the rollback with one click.
When to use it
Use it when cache rules, Page Rules, or `_headers`/CDN config live in a Git repo and a bad edit can silently collapse hit ratio — driving up origin load and bills before anyone notices. It turns a slow, after-the-fact incident into a pre-staged fix.
How it works
- 1Schedule fires every 15 minutes.
- 2Cloudflare returns current and trailing-baseline cache hit ratio for the zone.
- 3A logic step checks whether the drop exceeds the threshold; if not, the run ends quietly.
- 4GitLab is queried for the latest merged commit touching the edge-config path, which becomes the rollback target.
- 5GitLab creates a revert branch and opens a merge request titled with the regression details.
- 6Slack posts the MR link and the before/after ratio to the on-call channel.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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.