DEVOPS
Correlate flaky failures with Honeycomb traces and start a Slack triage thread
When a flaky test recurs, pulls the matching CI trace from Honeycomb, has an agent reason about the likely root cause (timing, resource contention, network), and opens a Slack…
How it runs
The automated pipeline, trigger to output.
- TriggerFlake-detected webhook receivedHTTP webhook
- ActionFetch CI run trace spans from HoneycombHoneycomb
- LogicAgent classifies likely root cause from spans
- LogicBranch: quarantine vs fix-first recommendation
- OutputOpen Slack triage thread with recommendationSlack
What it does
This workflow links an intermittent test failure to telemetry. On a flake event it fetches the related CI execution trace from Honeycomb, then an agent analyzes span timings and errors to hypothesize whether the failure is a race condition, a slow dependency, resource contention, or genuine product bug. It starts a Slack triage thread summarizing the evidence and a suggested quarantine-or-fix call.
When to use it
Use it when flakes are hard to diagnose and your team wastes triage time guessing. Pairing the failure with trace data turns a vague flake into an actionable hypothesis.
How it works
- 1A flake-detected webhook fires with the test identifier and run timestamp.
- 2The workflow queries Honeycomb for the trace spans covering that test run.
- 3An agent reviews span latencies, retries, and errors to classify the likely cause.
- 4A branch decides whether the evidence points to test infrastructure (recommend quarantine) or product code (recommend fix-first).
- 5It opens a Slack thread with the trace summary, classification, and recommendation, mentioning the owning team.
- 6The Slack thread link is returned as output.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 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 DevOps workflows
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.