DEVOPS
Daily DORA scorecard from GitLab merges + Honeycomb deploys
Each morning, joins yesterday's GitLab MR merge events with Honeycomb deploy markers to compute per-team deploy frequency and change lead time.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily 7am schedule (prior 24h window)
- ActionFetch merged MRs from GitLabGitLab
- ActionFetch deploy markers from HoneycombHoneycomb
- LogicJoin markers to MRs by SHA, compute lead time + deploy counts
- ActionAppend scorecard rows to BigQueryBigQuery
- OutputPost per-team digest to SlackSlack
What it does
Produces a daily, per-team DORA scorecard for the two flow metrics: deployment frequency and change lead time. It pairs each merged GitLab merge request with the Honeycomb deploy marker that shipped it, derives lead time (merge to deploy), counts deploys per team, persists the rows to BigQuery, and drops a readable summary in Slack.
When to use it
Run this when engineering leadership wants a trustworthy daily pulse on delivery throughput without anyone hand-assembling spreadsheets. Ideal for orgs that merge in GitLab and emit deploy markers to Honeycomb but lack a unified DORA view.
How it works
- 1A scheduled trigger fires at 7am for the prior 24-hour window.
- 2Pull merged MRs from GitLab, tagging each with its owning team via project-to-team mapping.
- 3Pull Honeycomb deploy markers for the same window.
- 4Logic step joins markers to MRs by commit SHA and computes per-MR lead time and per-team deploy counts.
- 5Append the computed scorecard rows to a BigQuery DORA table for history.
- 6Post the formatted per-team digest to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect HoneycombDistributed traces and queries.
- 3Connect BigQueryDatasets, queries, schemas.
- 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.