Seiri Documentation

Works with all popular integrations

Add one curl to your crontab line and get alerted when a scheduled job fails or never runs.

Ping from CronJob containers, or install seiri-kube-agent from the Helm repo to report workload health.

Check in by email from locked-down or legacy hosts that can't make outbound HTTP requests.

Show customers and teammates the health of the jobs and services you monitor.

Missed-run detection
Each monitor has an expected schedule and grace period. If the ping doesn't arrive in time, Seiri alerts you.
Explicit failure pings
Call /fail when a job exits non-zero to alert at once, without waiting for the grace period.
Cron, periodic, or on-demand
Match the monitor to how the job runs: a cron expression, a fixed interval, or work triggered by events.
Email heartbeats
Hosts that can't make outbound HTTP calls can check in by sending an email to the monitor's address.
Kubernetes agent
seiri-kube-agent reports Deployment, Job, and Pod health from HealthCheck resources. Available on Growth and Scale.
Alerts where you work
Slack, Discord, Microsoft Teams, Telegram, email, SMS, and outgoing webhooks.
Check-in history
See every ping, its source and payload, and when each run was missed or failed.
Status pages and SLAs
Publish job and service health to customers, and track SLA targets per monitor.
API, CLI, Terraform, MCP
Create and manage monitors as code, or from an AI assistant via the MCP server.

How a ping becomes a status: on time, late, missed, or failed, and when each one alerts.

Every ping a monitor received, with timestamps, source, and any payload your job sent.

What Seiri guarantees about check-ins, grace periods, and the difference between a missed and a failed run.

Find runs that reported /fail or never checked in, and see what the job sent.

Each monitor's ping URL, with its /success and /fail variants.