DEVOPS
Deploy-frequency drop detector comparing Honeycomb markers to baseline
Twice daily, counts recent Honeycomb deploy markers per service against each service's 30-day baseline from BigQuery, and alerts Slack when deploy frequency falls sharply.
How it runs
The automated pipeline, trigger to output.
- TriggerTwice-daily schedule
- ActionCount recent deploy markers per service from HoneycombHoneycomb
- ActionRead 30-day baselines from BigQueryBigQuery
- LogicCompute deviation, flag below-threshold services
- ActionEnrich flagged services with GitLab project + mergesGitLab
- OutputPost anomaly alert to SlackSlack
What it does
Detects when a service quietly stops shipping. It tallies deploy markers from Honeycomb over a recent window, compares each service to its own trailing 30-day deploy-frequency baseline stored in BigQuery, and raises a Slack alert only when a service drops materially below normal cadence, including the linked GitLab project so the owner is obvious.
When to use it
Reach for this when slowed delivery is a leading indicator you care about catching early. Unlike the daily scorecard, this focuses purely on cadence anomalies rather than full DORA reporting.
How it works
- 1A twice-daily schedule trigger fires.
- 2Pull recent deploy markers per service from Honeycomb.
- 3Read each service's 30-day deploy-frequency baseline from BigQuery.
- 4Logic step computes the deviation and flags services below the drop threshold.
- 5Action enriches flagged services with their owning GitLab project and recent merge activity.
- 6Output posts a focused anomaly alert to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect GitLabRepos, MRs, pipelines, registry.
- 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.