DEVOPS
Daily Latency Percentile Trend to Notion Capacity Brief
Each morning this workflow pulls 24-hour p50/p95/p99 trends from Honeycomb, compares them against the previous week.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily scheduled run
- ActionQuery Honeycomb 24h and trailing-week percentiles per serviceHoneycomb
- LogicClassify each service by percentile drift and headroom
- ActionFormat per-service capacity brief with recommendations
- OutputWrite dated capacity brief to Notion databaseNotion
What it does
Runs on a daily schedule, fetches the last 24 hours of p50/p95/p99 latency per service from Honeycomb, compares the percentiles against the trailing-week baseline, and publishes a capacity brief to Notion. Each service gets a clear verdict: scale up, hold, or scale down, with the percentile drift that justifies it.
When to use it
Use it for proactive weekly capacity planning instead of reactive firefighting. It surfaces slow latency creep that never trips an alert but signals you are running out of headroom or over-provisioned.
How it works
- 1A scheduled trigger runs every morning.
- 2The flow queries Honeycomb for 24-hour and trailing-week p50/p95/p99 per service.
- 3A logic step classifies each service by percentile drift versus baseline and headroom thresholds.
- 4It formats a per-service capacity brief with recommendations and trend deltas.
- 5It writes or updates the brief as a dated page in the Notion capacity database.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect NotionPages, databases, comments.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.