DEVOPS
Archive Nightly Handoff Metrics to BigQuery
Each morning, rolls up the night's PagerDuty and Axiom incident data into structured rows, writes them to BigQuery for long-term on-call health tracking.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires after overnight window
- ActionFetch PagerDuty incidents and response timesPagerDuty
- ActionQuery Axiom for off-hours alert volumeAxiom
- LogicCompute rollup metrics and shape rows
- ActionInsert rows into BigQuery metrics tableBigQuery
- OutputEmail daily snapshot to eng lead via GmailGmail
What it does
This workflow treats the handoff as data, not just a message. Each morning it computes the night's on-call metrics — incident count, mean time to acknowledge, mean time to resolve, after-hours page count, and noisiest service — from PagerDuty and Axiom, appends them as structured rows in BigQuery, and emails a snapshot to the engineering lead. Over weeks this becomes a trend line for on-call burden.
When to use it
Use it when you need to measure and report on-call health over time — for staffing decisions, rotation fairness, or showing leadership that paging volume is trending down. It complements a human-readable handoff with durable metrics.
How it works
- 1A daily schedule fires after the overnight window closes.
- 2Fetch the night's incidents and response times from PagerDuty.
- 3Query Axiom for off-hours alert volume and error counts.
- 4A logic step computes the rollup metrics and shapes them into rows.
- 5Insert the rows into the BigQuery on-call metrics table.
- 6Email the daily snapshot to the engineering lead via Gmail.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect AxiomLog streams, queries, dashboards.
- 3Connect BigQueryDatasets, queries, schemas.
- 4Connect GmailRead, draft, send, label.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
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.
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…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.