ingestlayer/recipes

Monitor cron-job health in Email

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

  • toemail.outEmail
    toalerts@acme.com

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 Email

Send a transactional email to one or more recipients, addressable from event fields.

  1. 01

    set the recipient

    Enter a fixed address, or reference an event field like $event.payload.email to route per event.

  2. 02

    write subject and body

    Both accept $event.* templates. The body renders as plain text with an optional summary table of the payload.

  3. 03

    confirm the sender

    Mail goes out from mail@notify.ingestlayer.com with SPF and DKIM aligned. Set a reply-to if you want responses to reach you.

in emaildelivered
From:    mail@notify.ingestlayer.com
To:      alerts@acme.com
Subject: Payment failed — acme-inc (€240.00)

A charge failed for 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 Email