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 Telegram

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

totelegramTelegram
chat@oncall

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 Telegram

Message a person, group, or channel through a connected bot.

01
connect a bot
Create a bot with @BotFather and paste its token. We register the webhook and verify it in-region.
02
start a chat
Send /start to the bot from the target chat — or add it to the group/channel — then pick the chat from the list.
03
format the text
Messages use MarkdownV2; the default template bolds the event name and lists fields. Reserved characters in field values are escaped for you.

in telegramdelivered

oncall
*support.ticket.created*
ticket    T-4821
subject   API returning 500s
tier      enterprise
urgency   critical

notes

Telegram caps a bot at roughly 30 messages per second overall, and one per second to a single chat.
The bot must be added to a group — and promoted to admin for a channel — before it can post.
MarkdownV2 requires escaping characters like _ * [ ] ( ); ingestlayer escapes field values, but custom templates are your responsibility.

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 →