ENGINEERING
Post a daily error-budget health digest to Microsoft Teams
Each morning, pulls remaining error budget and burn rate for every tracked Honeycomb SLO and posts a ranked health digest to Microsoft Teams.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionList SLOs and fetch budget and burn rate from HoneycombHoneycomb
- LogicRank services and flag those near the freeze floor
- OutputPost ranked error-budget digest to Microsoft TeamsMicrosoft Teams
What it does
Gives the team a once-a-day snapshot of every SLO's error-budget health before anyone ships. It ranks services by remaining budget and burn trajectory so engineers know which areas are fragile and should avoid risky changes today.
When to use it
Use it for proactive budget awareness rather than reactive paging. A standing morning digest keeps reliability visible during planning and standup, so freezes rarely come as a surprise.
How it works
- 1A daily schedule triggers the flow before the workday starts.
- 2The flow lists all tracked SLOs in Honeycomb and fetches each one's remaining budget and current burn rate.
- 3A logic step ranks services and tags any below the warning floor as at-risk-of-freeze.
- 4It formats a digest: healthy SLOs summarized, at-risk ones called out with numbers and trend.
- 5It posts the digest to the engineering Microsoft Teams channel as an adaptive message with links to each SLO.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.