ENGINEERING
Open a GitHub issue from a Datadog APM latency-spike alert
When a Datadog APM monitor alerts on a latency regression, fetches the slowest trace, extracts the offending span and SQL.
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog APM latency monitor webhook firesDatadog
- ActionFetch exemplar trace and span breakdown from DatadogDatadog
- LogicParse dominant span; confirm regression is query-bound
- ActionResolve owning repo and create labeled GitHub issueGitHub
- OutputNotify on-call in Slack with issue linkSlack
What it does
Reacts to a Datadog APM latency monitor alert by pulling the exemplar trace behind the spike, identifying the slowest span and its database call, and opening a GitHub issue in the service's repository with everything an engineer needs to reproduce.
When to use it
When your alerting lives in Datadog but your engineers work issues in GitHub. Use it to close the gap between a paging-grade latency alert and a tracked, repo-scoped bug rather than re-investigating from scratch.
How it works
- 1A Datadog monitor webhook fires when APM latency breaches the threshold.
- 2Fetch the exemplar trace and span breakdown from the Datadog Trace API for the alerting service.
- 3A logic step parses out the dominant span and its `db.statement`, confirming the regression is query-bound and not network.
- 4Look up the owning GitHub repo from the service tag mapping.
- 5Create a GitHub issue with the slow query, latency delta vs. baseline, affected endpoint, and a Datadog trace permalink, labeled `performance`.
- 6Notify the on-call engineer in Slack with the issue link.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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
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.
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.
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.
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…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.