DEVOPS
Real-time lead-time capture on each Honeycomb deploy marker
When Honeycomb records a new deploy marker, it looks up the GitLab MRs in that deploy, computes change lead time for each.
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb deploy marker webhookHoneycomb
- ActionResolve included MRs from GitLab commit rangeGitLab
- LogicCompute per-MR lead time + release rollup
- ActionStream deploy record to BigQueryBigQuery
- OutputReturn record id confirmation
What it does
Captures change lead time at the moment of deploy instead of in a nightly batch. Every time Honeycomb fires a deploy marker, this workflow resolves which GitLab merge requests are included in that release, calculates merge-to-deploy duration for each, and writes one immutable deploy record to BigQuery.
When to use it
Choose this over a daily batch when you deploy many times a day and want near-live lead-time data, or when you need a clean event-sourced BigQuery table that downstream dashboards can aggregate however they like.
How it works
- 1A webhook trigger receives the Honeycomb deploy marker payload (service, environment, commit range).
- 2Action queries GitLab for the MRs merged within that commit range.
- 3Logic step computes lead time per MR and rolls up deploy size and median lead time for the release.
- 4Action streams the structured deploy record into BigQuery via streaming insert.
- 5Output confirms the write and emits the record id for traceability.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect BigQueryDatasets, queries, schemas.
- 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.