ingestlayer/recipes

Monitor cron-job health in Discord

Hear about the scheduled jobs that fail or run long — and only those — so a silent backup or a stalled sync becomes a message, not a surprise.

01source

sourcesdk.eventTypeScript SDK
matchcron.finished

02pipeline · 1 steps

  • 01CTLfilter.matchstatus = failed or ran long

03destinations · 1

  • todiscordDiscord
    channel#ops

the event

You emit cron.finished with this shape. The TypeScript SDK keeps the call type-safe, and the event is stored whole — so every field below is available to the pipeline by name.

  • jobstringjob name
  • statusstringok | failed
  • duration_msnumber
  • expected_msnumbertypical runtime
  • exit_codenumber

emit it

From your code with the TypeScript SDK — or any language over the REST endpoint and signed webhook ingress.

emit cron.finished
import { ingest } from "@ingestlayer/sdk";

await ingest("cron.finished", {
  job:         "nightly-backup",
  status:      ok ? "ok" : "failed",
  duration_ms: Date.now() - startedAt,
  expected_ms: 120000,
  exit_code:   code,
});

route it to Discord

Send rich embeds to a channel via a connected bot or a channel webhook.

  1. 01

    connect the bot

    Add the ingestlayer bot to your server, or paste a channel webhook URL. Either credential is held in-region.

  2. 02

    choose the channel

    Select the target channel from the picker. Each connected channel is one reusable destination row.

  3. 03

    shape the embed

    The default embed carries the event name as its title and the payload as name/value fields; override with $event.* references.

in discorddelivered
┌─ #ops ─────────────────────────────────┐
│ ▎ payment.failed                        │
│ ▎ customer   acme-inc                   │
│ ▎ amount     €240.00                    │
│ ▎ reason     insufficient_funds         │
│ ▎ attempt    2                          │
└─────────────────────────────────────────┘

notes

questions

Can I only hear about problems?
Filter to failures and jobs that overran their expected_ms; healthy runs pass silently to the warehouse for the record.
How do I catch a job that never ran?
Pair this with a scheduled check that emits when an expected cron.finished is missing — absence is the signal there.
Can different jobs alert different teams?
Branch on the job name so a failed billing run reaches finance and a failed deploy reaches engineering.
build this pipelineor read the quickstart →

cron-job health, routed elsewhere

more, into Discord