ENGINEERING
Datadog error-rate anomaly to PagerDuty + GitHub issue
When Datadog detects an anomalous error-rate climb on a service, it pages the on-call via PagerDuty and opens a GitHub issue pre-filled with the affected service, metric…
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog monitor enters alert on error-rate anomalyDatadog
- LogicFilter for triggering transition, ignore recovery/warn
- ActionTrigger PagerDuty incident on the service escalation policyPagerDuty
- ActionOpen GitHub issue with metric snapshot and runbook linkGitHub
- OutputAttach GitHub issue URL to the PagerDuty incidentPagerDuty
What it does
Bridges Datadog's anomaly detection to both human escalation and a durable engineering record: the on-call gets paged immediately, and a GitHub issue is opened so the incident has a place to live after the page is acknowledged.
When to use it
Use it for production services where error-rate anomalies need a real human now and a follow-up paper trail. Ideal when GitHub Issues is your source of truth for postmortems and PagerDuty owns escalation.
How it works
- 1A Datadog monitor in alert state hits the workflow webhook with the service, metric, and anomaly window.
- 2A filter confirms the alert is a triggering transition (not a recovery or warn) before escalating.
- 3PagerDuty receives a triggered incident routed to the service's escalation policy.
- 4A GitHub issue is created in the service repo with the metric snapshot, time window, dashboard link, and the matching runbook.
- 5The PagerDuty incident is updated with the GitHub issue URL so responders jump straight to the tracking record.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.