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 Postgres

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

towarehouse.pgPostgres
tableevents.signups

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 Postgres

Insert each event as a row into a table in your own Postgres.

01
add the connection
Paste a Postgres connection string. Connections originate from our EU region — allowlist those egress IPs on your database.
02
point at a table
Name the target table. Top-level event fields map to columns, and the full payload is also available as a jsonb column.
03
map columns
Match event fields to columns with $event.* references, or accept the default mapping into a typed events table.

in postgresdelivered

INSERT INTO events.signups
  (user_id, email, plan, source, payload)
VALUES
  ('u_018f', 'ada@acme.com', 'pro',
   'marketing-site', '{ … }'::jsonb);

notes

The target table must already exist with compatible column types; ingestlayer never runs DDL on your database.
Connections come from fixed EU egress IPs — add them to your firewall, or inserts will time out.
Use a jsonb column for the full payload when your event shape changes often, so a new field never breaks the insert.

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 →