Better Stack

Pull up every uptime monitor you're running so you can see what's being watched at a glance

Ask for one monitor and get its settings and current status without digging through the dashboard

Set up a new uptime check on any endpoint just by describing what you want watched

Change a monitor's URL, interval, or alerting in one request instead of clicking through settings

Remove a monitor you no longer need and stop the checks tied to it

Temporarily stop checks during planned work so you don't get false alerts

Bring a paused check back online the moment maintenance wraps up

See how fast an endpoint is responding and catch slowdowns before they turn into outages

Get a monitor's uptime and SLA numbers for reporting or a quick health read

View how your monitors are organized into groups across services or environments

Look up a single monitor group and the checks it contains

Bundle related monitors into a new group to keep a large fleet tidy

Rename or reorganize a monitor group as your services change

Clear out a group you no longer use to keep the dashboard clean

See all your cron and background-job heartbeats and which ones are reporting on time

Look up one heartbeat to confirm a scheduled job is still checking in

Add a check for a cron or background job so a silent failure never slips past you

Adjust a heartbeat's expected period or alerting as your job schedule shifts

Retire a heartbeat for a job you've stopped running

View how your job heartbeats are grouped for easier tracking

Pull up one heartbeat group and the jobs it covers

Group related job heartbeats together to keep background work organized

Rename or restructure a heartbeat group as your jobs evolve

Remove a heartbeat group you no longer need

See open and past incidents in one view so you know what's on fire and what's settled

Ask for a single incident and get its status, cause, and who's on it

Open an incident by hand when something breaks that a monitor didn't catch

Claim an open incident so the team knows someone is handling it and escalation stops

Close out an incident once the issue is fixed and record it as done

Remove an incident that was logged in error

Trace an incident from first alert to resolution for a clean postmortem

See every on-call schedule and who's carrying the pager across your teams

Look up one schedule to confirm who's on call right now

Review how alerts hand off between responders when no one answers

Pull up a single policy to check its steps and timing

See all your public and internal status pages in one place

Look up one status page and its current configuration

Stand up a new public status page to keep customers informed during outages

Change a status page's branding, domain, or layout without leaving chat

Take down a status page you no longer publish

See how a status page is divided into sections for different service areas

Look up a single section on a status page and what it groups

Add a new section to organize services on your status page

Rename or rearrange a status page section as your services change

Remove a section from a status page you no longer need

See which monitors and services are displayed on a status page

Look up one resource shown on a status page and its current state

Put a monitor or service on your status page so visitors can see its health

Change how a resource appears or which service it tracks on a status page

Take a service off a status page when it no longer belongs there

See who's subscribed to updates from your status page

Sign someone up for status page notifications so they hear about outages

Unsubscribe someone from status page updates on request

Review the incident and maintenance reports posted to a status page

Look up one status page report and its full history

Publish an incident or maintenance notice to your status page in seconds

Revise a published report as the situation develops

Remove a status page report that's no longer relevant

See the running updates attached to a status page report

Add a fresh update to an ongoing incident so customers stay in the loop

Fix or refine an update you've already posted to a report

Take down a report update that was posted by mistake

Pull catalog attributes and metadata to understand how your account is set up

Change catalog attributes and metadata to keep your setup accurate

See which tools are wired into Better Stack for alerts and routing

View everyone on your Better Stack team and their roles

Look up one team member's details and access

Reach any part of the Better Stack Uptime API for requests the ready-made actions don't cover

Fires when Better Stack opens a new incident because a monitor check failed.

Fires when a responder acknowledges an open incident in Better Stack.

Fires when an incident is resolved, either automatically on recovery or manually by a responder.

Fires when a responder posts a new comment / update on an incident.

Fires when an unacknowledged incident escalates to the next step of the on-call policy.

Fires when a monitor's check fails and the endpoint is considered down.

Fires when a previously down monitor recovers and its check passes again.

Fires when a new monitor is added in Better Stack.

Fires when a monitor is paused and stops running checks.

Fires when a heartbeat does not report within its expected period — a cron/background job failed to check in.

Fires when a previously missed heartbeat checks in again.

Fires when a new on-call shift begins for a user in a schedule.

Fires ahead of an on-call shift ending so the next responder can be reminded.

Fires when a new incident is published to a public Better Stack status page.

Fires when a published status page incident gets a new update or status change (e.g. monitoring, resolved).