One-line check-ins
Ping the reusable telemetry URL from curl, a Kubernetes CronJob, GitHub Actions, or the Telesis CLI. The full URL is shown once after creation or rotation.
Cron jobs
Give every scheduled job a deadline you can see.
Attach a scheduled job to a monitored service and send a lightweight HTTP check-in. Telesis detects missed, failed, and timed-out runs; completion-only is the default, with optional start and fail events.
Illustrative product preview
Nightly backup
0 2 * * * · UTC
Started
12 Jul · 02:00:04 UTC
Completed
12 Jul · 02:04:12 UTC
Next expected
13 Jul · 02:00:00 UTC
Completion-only check-inSucceeded
What you get
Late and missed deadlines
Use a fixed interval or five-field cron expression with an IANA timezone and an editable grace period.
Optional run lifecycle
Add start and fail events, duration, exit code, and a maximum runtime when completion-only telemetry is not enough.
Service-aware response
Route failures through existing alert rules and offer incident creation without publishing anything automatically.
Why teams pick it
- Completion-only by default; start and fail events stay optional
- Waits for the first accepted event before deadline alerts can arm
- Failures remain internal unless service-health impact is explicitly enabled
- One backing check reuses alert, incident, retention, and permission workflows