IT OPS

Daily Edge Fleet Health Digest to Discord

Posts a once-a-day Discord summary of edge fleet health — devices currently down, flappy boxes, and the worst sites by total downtime over the last 24 hours.

CategoryIT Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionQuery 24h heartbeat history from PostgresPostgreSQLPostgres
  • LogicAggregate down counts, flaps, downtime totals
  • LogicRank sites by accumulated downtime
  • OutputPost fleet health digest to DiscordDiscordDiscord

What it does

Delivers a morning readout of the whole edge fleet so the team sees patterns the per-incident alerts miss. It rolls up the last 24 hours from the heartbeat ledger into counts of healthy versus down devices, highlights boxes that repeatedly flapped, and ranks the sites with the most accumulated downtime.

When to use it

Use it for a daily standup signal or to catch chronically unreliable hardware that recovers fast enough to dodge paging. It turns raw heartbeat history into an at-a-glance fleet scorecard.

How it works

  1. 1A daily schedule fires each morning before standup.
  2. 2An action queries Postgres for every device's heartbeat history over the trailing 24 hours.
  3. 3A logic step aggregates the data: current down count, flap count per device, and downtime totals per site.
  4. 4A logic step ranks sites by accumulated downtime and selects the top offenders.
  5. 5The workflow posts a formatted digest to the team's Discord ops channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect DiscordCommunity channels + voice + bots.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.