ENGINEERING
Daily GitLab CI Stage-Timing Digest to Honeycomb & Slack
Runs each morning, pulls the prior day's pipeline runs from GitLab, emits per-stage duration metrics to Honeycomb for trend dashboards.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled daily run
- ActionQuery prior-day GitLab pipelines and stagesGitLab
- ActionEmit per-stage duration events to HoneycombHoneycomb
- LogicRank stages by week-over-week drift
- OutputPost movers digest to SlackSlack
What it does
Each morning it gathers the previous day's default-branch pipeline runs, breaks each into its stages, and ships per-stage duration events to Honeycomb so you build long-horizon trend boards. It then posts a short Slack digest naming the two or three stages that drifted slowest versus the prior week.
When to use it
Use it when you want continuous observability of CI health rather than only reacting to a single bad run. It feeds Honeycomb the structured timing data needed for week-over-week heatmaps while giving the team a readable daily pulse without opening a dashboard.
How it works
- 1A scheduled trigger fires every morning.
- 2The flow queries GitLab for all default-branch pipelines from the prior 24 hours and expands their jobs by stage.
- 3Each stage's duration is sent to Honeycomb as a structured event with stage, pipeline, and commit attributes.
- 4A logic step ranks stages by their change against the trailing week's average.
- 5A Slack message posts the top movers with arrows and durations to the engineering channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect HoneycombDistributed traces and queries.
- 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 Engineering workflows
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
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.