DEVOPS
Replicate Cold-Start SLO Breach to PagerDuty
Triggers on a Datadog cold-start latency monitor alert, confirms the breach against live Replicate metrics.
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog cold-start latency monitor alertDatadog
- ActionConfirm breach against live Replicate predictionsReplicate
- LogicSustained breach across multiple predictions?
- OutputOpen PagerDuty incident with contextPagerDuty
What it does
This workflow turns a noisy latency signal into a trustworthy page. When Datadog detects that Replicate cold-start latency has breached your SLO, the flow double-checks the breach against live Replicate prediction data before deciding whether to wake anyone up. Transient single-request spikes are dropped; sustained degradation escalates to PagerDuty.
When to use it
Use it when a Replicate endpoint backs a production feature with a latency SLO and you want on-call paged for genuine cold-start storms — not every momentary blip a raw monitor would fire on.
How it works
A Datadog monitor webhook triggers the flow on a latency-threshold alert. An action queries Replicate for the most recent predictions to confirm cold starts are actually elevated right now. A logic step requires the breach to be sustained across multiple recent predictions, not a one-off. If confirmed, the flow opens a PagerDuty incident with the measured latency, model version, and a link back to the Datadog graph. If it was a false alarm, it resolves quietly without paging.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect ReplicateImage, video, and model inference.
- 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 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.