Activity & Logbook

The CLI has two commands for monitoring account activity. Both mirror their counterparts on the web dashboard, using the same calculations and terminology so the numbers are always consistent.

steadycron report — activity overview

steadycron report                  # last 24 h (default)
steadycron report --hours 168      # last 7 days (Developer plan and above)
steadycron report --hours 720      # last 30 days (Team plan)
steadycron report --verbose        # include HTTP response bodies and full alert list
steadycron report --json           # machine-readable output for CI or dashboards

Calls /api/reports/summary and prints the same figures shown on the web Overview page. The success rate is calculated as successful_checks / total_checks (covering both HTTP executions and heartbeat pings), so the CLI and the dashboard always agree for an identical time window.

Section	What you see
KPI row	Total checks, Successful + success-rate %, Incidents (failed checks), Alerts delivered / failed / suppressed, Jobs reporting
Active issues	Jobs with failures or missed check-ins, ranked by attention severity (missed → abandoned → failure → late)
Silent monitors	Jobs with zero activity in the window — possible misconfiguration or schedule drift
Footer	One-line health verdict; exits non-zero when failures or undelivered alerts are present

--json emits the raw API response, useful for scripted alerting or feeding a custom dashboard.

Plan limits

Plan	Maximum --hours
Free	24
Developer	168 (7 days)
Team	720 (30 days)

The server returns a range_exceeds_plan error with a clear message if the requested window exceeds your plan’s limit.

steadycron logbook — full event history

steadycron logbook                                       # last 24 h, all event types
steadycron logbook --hours 168                           # last 7 days
steadycron logbook --domain executions                   # filter by category
steadycron logbook --domain executions --domain alerts   # multiple categories (repeatable)
steadycron logbook --severity critical                   # critical events only
steadycron logbook --job my-job-key                      # events for one job
steadycron logbook --page 2 --page-size 100             # paginate
steadycron logbook --all                                 # fetch every page
steadycron logbook --verbose                             # full per-event metadata
steadycron logbook --all --json                          # machine-readable output

Mirrors the web Logbook page. Each event shows a severity indicator, timestamp, event label, job name (where applicable), and a short detail string. --verbose adds per-event metadata fields: HTTP status code, error type, response body excerpt, source IP, and more.

Domains

Filter by event category with --domain (repeatable):

Domain	Events included
executions	HTTP execution succeeded, HTTP execution failed
heartbeats	Heartbeat missed, heartbeat recovered, ping received, run started, run abandoned
alerts	Alert delivered, alert delivery failed, alert suppressed, alert pending
jobs	Job created, job deleted, job paused, job resumed
keys	API key created, API key revoked
rules	Alert rule created, alert rule deleted
channels	Alert channel created, alert channel updated, alert channel deleted
subscription	Plan upgraded, plan downgraded, subscription canceled, subscription past due, subscription paused

Severity

Filter by severity with --severity (repeatable): info, warning, or critical.

Pagination

By default, logbook returns the first 50 events (adjust with --page-size, max 100). Use --page N to navigate pages, or --all to fetch every matching event across all pages in one go.

Job filter

--job accepts a job key (preferred), job name, or job id (GUID). The job key is the stable identifier shown in the Key column of steadycron jobs list and is stable across job renames.