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.

Monitor cron-job health in Webhook

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

towebhook.outWebhook
urlhttps://api.acme.com/hooks

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 Webhook

POST the processed event as JSON to any HTTPS endpoint you control.

01
set the URL
Any HTTPS endpoint. The processed event is delivered as a JSON body on POST.
02
choose auth
None, a bearer token, or HMAC signing. Signed requests carry an X-Ingestlayer-Signature header you verify with your shared secret.
03
confirm receipt
Return a 2xx within the timeout. Non-2xx responses trigger retries with exponential backoff before the delivery dead-letters.

in webhookdelivered

POST /hooks HTTP/1.1
Host: api.acme.com
Content-Type: application/json
X-Ingestlayer-Signature: t=1717000000,v1=9f86d08…

{
  "type": "user.signed_up",
  "payload": { "email": "ada@acme.com", "plan": "pro" }
}

notes

Endpoints must respond within 10 seconds; slower responses are treated as failures and retried.
Retries use exponential backoff for several attempts before dead-lettering — make your handler idempotent.
Verify the HMAC signature before trusting a payload; the raw body is signed, so compute the digest before JSON parsing.

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 pipeline or read the quickstart →