ENGINEERING
Lock-Contention Watchdog with PagerDuty Escalation
Polls pg_stat_activity every minute for queries blocked on locks beyond a duration threshold, posts the blocking chain to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerOne-minute schedule
- ActionRead activity and lock graphPostgres
- LogicFind blockers past threshold and SLA
- OutputPost blocking chain to SlackSlack
- OutputEscalate sustained blocker to PagerDutyPagerDuty
What it does
It catches lock pileups before they take down throughput. Every minute it reads `pg_stat_activity` and `pg_locks` to build the blocking-chain graph, identifies any query waiting on a lock longer than the threshold, and surfaces the head blocker. A short wait posts a Slack heads-up with the blocking PID, query text, and wait duration; a sustained blocker past the SLA escalates to PagerDuty so on-call can decide whether to terminate it.
When to use it
Use this when long-running transactions or migrations occasionally block writes and the first symptom today is a flood of timeouts. It gives you the blocking chain and an actionable PID instead of guesswork.
How it works
- 1A one-minute schedule fires.
- 2Query `pg_stat_activity` and `pg_locks` for the blocking chain.
- 3A logic step finds blockers past the wait threshold and SLA.
- 4Post the blocking chain and culprit PID to Slack.
- 5If the blocker exceeds the SLA, page on-call via PagerDuty.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.