Getting Started Overview
Seiri provides push/heartbeat monitoring for jobs, cron, and workers — create a webhook, copy the ping URL, and check in when work finishes.
Tip: All monitors live under Core → Webhooks. Types are Periodic, Cron, and On-Demand.
How Seiri Works
1. Check-in intake
- Your job sends a GET/POST to
https://ping.seiri.app/webhook/<endpoint-id>/success(or/fail) - Or emails the monitor’s
@ping.seiri.appaddress - Each check-in is recorded as an event
2. Missed-run detection
- Periodic and Cron monitors expect check-ins on a schedule
- If a ping is late past the grace period, Seiri marks a miss and can alert
3. Alerts and insights
- Notify Slack, Discord, email, SMS, Teams, Telegram, Ntfy, or a webhook
- Inspect history via Dashboard, webhook stats, or Services → Cron Jobs
Typical setup flow
- Sign in at cloud.seiri.app
- Open Core → Webhooks → + Create Webhook
- Choose type Periodic, Cron, or On-Demand
- Copy the endpoint URL from the ENDPOINT column
- Ping
ping.seiri.appafter successful runs - Configure alerts and verify stats
Tip: Use Cron / Periodic for recurring jobs; On-Demand when there is no expected cadence.
Canonical recipe: Integrate a job.
Why use Seiri
- Detect silent job failures — know when cron or workers stop checking in
- Alert before users notice — Slack, Discord, email, and more
- Push-based, not uptime polls — Seiri is not website uptime monitoring
- Minimal setup — one HTTP call (or one email) at the end of the job
FAQ
How long does setup take?
Most users can start monitoring within a few minutes.
Do I need an SDK to use Seiri?
No. You can start with simple HTTP requests or webhooks. SDKs are optional.
Can Seiri monitor internal jobs?
Yes. Any job that can send a heartbeat or execution status can be monitored.
Is Seiri environment-aware?
Yes. Development, staging, and production environments are fully isolated.
What’s the next step after this page?
Go to the Quickstart to configure your first webhook or scheduled job.