Skip to content

CLI Reference

Manage status pages, monitors, and incidents from the terminal.

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] [COMMAND] [COMMAND FLAGS] [ARGUMENTS...]

Global flags:

NameDescriptionDefault valueEnvironment variables
--jsonOutput results as JSONfalsenone
--no-colorDisable colored outputfalsenone
--quiet (-q)Suppress non-error outputfalsenone
--debugEnable debug outputfalsenone

Manage your monitors.

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] monitors [ARGUMENTS...]

Create or update monitors.

openstatus monitors apply openstatus monitors apply —config custom.yaml -y openstatus monitors apply —dry-run

Creates or updates monitors according to the OpenStatus configuration file. Compares your openstatus.yaml with the current state and applies changes.

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] monitors apply [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--config="…" (-c)The configuration file containing monitor informationopenstatus.yamlnone
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN
--auto-accept (-y)Automatically accept the promptfalsenone
--dry-run (-n)Show what would be changed without applyingfalsenone

Create monitors.

openstatus monitors create openstatus monitors create —config custom.yaml -y

Create the monitors defined in the openstatus.yaml file.

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] monitors create [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--config="…" (-c)The configuration file containing monitor informationopenstatus.yamlnone
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN
--auto-accept (-y)Automatically accept the promptfalsenone

Delete a monitor.

openstatus monitors delete MonitorID openstatus monitors delete 12345 -y

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] monitors delete [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN
--auto-accept (-y)Automatically accept the promptfalsenone

Import all your monitors.

openstatus monitors import openstatus monitors import —output monitors.yaml

Import all your monitors from your workspace to a YAML file; it will also create a lock file to manage your monitors with ‘apply’.

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] monitors import [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN
--output="…" (-o)The output file nameopenstatus.yamlnone

Get a monitor information.

openstatus monitors info MonitorID openstatus monitors info 12345 openstatus monitors info 12345 —time-range 7d

Fetch the monitor information including configuration, live status per region, and summary metrics.

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] monitors info [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN
--time-range="…"Time range for summary metrics (1d, 7d, 14d)1dnone

List all monitors.

openstatus monitors list openstatus monitors list —all

List all monitors. The list shows all your monitors attached to your workspace. It displays the ID, name, URL, and kind of each monitor.

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] monitors list [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--allList all monitors including inactive onesfalsenone
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN

Trigger a monitor execution.

openstatus monitors trigger MonitorID openstatus monitors trigger 12345

Trigger a monitor execution on demand. This command allows you to launch your tests on demand.

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] monitors trigger [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN

Manage status reports.

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] status-report [ARGUMENTS...]

List all status reports.

openstatus status-report list openstatus status-report list —status investigating —limit 10

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] status-report list [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN
--status="…"Filter by status (investigating, identified, monitoring, resolved)none
--limit="…"Maximum number of reports to return (1-100)0none

Get status report details.

openstatus status-report info ReportID openstatus status-report info 12345

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] status-report info [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN

Create a status report.

openstatus status-report create —title “API Degradation” —status investigating —message “Investigating increased latency” —page-id 123

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] status-report create [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN
--title="…"Title of the status reportnone
--status="…"Initial status (investigating, identified, monitoring, resolved)none
--message="…"Initial message describing the incidentnone
--page-id="…"Status page ID to associate with this reportnone
--component-ids="…"Comma-separated page component IDsnone
--notifyNotify subscribers about this status reportfalsenone
--date="…"Date when the event occurred (RFC 3339 format, defaults to now)none

Update status report metadata.

openstatus status-report update ReportID [—title “New title”] [—component-ids id1,id2]

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] status-report update [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN
--title="…"New title for the reportnone
--component-ids="…"Comma-separated page component IDs (replaces existing list)none

Delete a status report.

openstatus status-report delete ReportID openstatus status-report delete 12345 -y

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] status-report delete [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN
--auto-accept (-y)Automatically accept the promptfalsenone

Add an update to a status report.

openstatus status-report add-update ReportID —status resolved —message “Issue has been resolved”

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] status-report add-update [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN
--status="…"New status (investigating, identified, monitoring, resolved)none
--message="…"Message describing what changednone
--date="…"Date for the update (RFC 3339 format, defaults to now)none
--notifyNotify subscribers about this updatefalsenone

Manage status pages.

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] status-page [ARGUMENTS...]

List all status pages.

openstatus status-page list openstatus status-page list —limit 10

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] status-page list [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN
--limit="…"Maximum number of pages to return (1-100)0none

Get status page details.

openstatus status-page info PageID openstatus status-page info 12345

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] status-page info [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN

Run your uptime tests.

openstatus run openstatus run —config custom-config.yaml

Run the uptime tests defined in the config.openstatus.yaml. The config file should be in the following format: tests: ids: - monitor-id-1 - monitor-id-2.

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] run [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--config="…"The configuration fileconfig.openstatus.yamlnone
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN

Get your workspace information.

openstatus whoami

Get your current workspace information. Displays the workspace name, slug, and plan.

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] whoami [COMMAND FLAGS] [ARGUMENTS...]

The following flags are supported:

NameDescriptionDefault valueEnvironment variables
--access-token="…" (-t)OpenStatus API Access TokenOPENSTATUS_API_TOKEN

Save your API token.

openstatus login

Saves your OpenStatus API token for use in subsequent commands. Get your API token from the OpenStatus dashboard.

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] login [ARGUMENTS...]

Remove saved API token.

openstatus logout

Usage:

Terminal window
$ openstatus [GLOBAL FLAGS] logout [ARGUMENTS...]