HTTP and Slack: Disk Usage Threshold Sweep Template
A scheduled sweep that pulls disk metrics from your hosts' metrics API and posts a Slack warning for any volume running low on free space.
What It Builds
A Schedule trigger fires on your cron of choice (say, every 15 minutes). A Connector node in Direct mode calls your metrics API over the http connector to fetch per-volume disk stats. A Loop walks each volume, a Condition checks it against your free-space threshold, and a slack Connector node posts a warning to your ops channel for anything over the line. Quiet runs stay silent so the channel only lights up when something needs attention.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow that runs every 15 minutes, calls our hosts' metrics API to get disk usage per volume, and for any volume with less than 15% free space posts a Slack warning to #infra-alerts with the host name, volume, percent free, and gigabytes remaining.
Connectors Used
- Schedule trigger - runs the sweep on a cron interval and time zone you set.
- http - Miraxa connects to your metrics API to read disk usage per volume.
- slack - posts the threshold warning to your chosen channel.
Customize It
Change the obvious knobs right in the prompt: the cron interval, the 15% free-space threshold, the metrics endpoint, the #infra-alerts channel, and the fields included in the message (add mount point, total size, or a host tag).
Tips
- Keep the metrics call in Direct mode for a fixed endpoint: it is exact and adds no AI cost.
- If your API needs a token, store it on the http connection so Spojit attaches it automatically.
- Add a second threshold tier (warn vs critical) with another Condition to route urgent volumes to a different channel.