Glossary

An A–Z of the terms used in SutramX and in these docs. Each entry links to the page that covers it in detail.

A#

Acknowledge. Marking an open incident as being handled. Acknowledging tells your team someone is on it and stops further escalation steps. See Incidents.

Active workspace. The workspace you're currently working in. The picker appears in the sidebar when you belong to more than one. See Workspaces.

Alert. A notification that a monitor went down or recovered. It's sent by email and through your connected channels. See How alerting works.

Alert contact (verified). An email address that gets alert emails for every monitor in the workspace. By default this is the workspace owner's verified account email.

Alert credits. The monthly allowance used by SMS, WhatsApp and voice-call alerts, with optional extra packs. See Alert credits.

Alert recipient. An email address chosen to receive alerts for a monitor or a monitor group. Addresses outside your team must confirm before they receive anything. See Email & push.

API key. A secret token that lets scripts and tools call the SutramX REST API on behalf of a workspace. The owner creates API keys in Account settings → API keys. See REST API.

API monitor. A monitor that calls an API endpoint and checks the response with assertions. See API & multi-step checks.

Assertion. A rule an API response must meet, such as a status code, header or value in the body.

B#

Browser push alerts. Alert notifications delivered by your web browser. Turn them on in Alerts → Channels & API. See Email & push.

C#

Channel. A destination for alerts other than plain email, such as Slack, Microsoft Teams, a webhook, PagerDuty or SMS.

Check. One attempt to reach a monitor's target from one location. Its result is up, degraded or down.

Check from / Locations. The setting that chooses which probe regions run a monitor's checks.

Check history. The list of a monitor's recent check results, shown on its detail page and exportable as CSV.

Check interval. How often a monitor is checked. The fastest interval you can pick depends on your plan.

Components. The monitors shown on a status page, optionally grouped into sections.

Confirmation. The steps SutramX takes before opening an incident: a retry, the failure threshold, and agreement between regions. See Regions & confirmation.

Cron job heartbeat. See Heartbeat monitor.

Custom domain. Your own domain, such as status.example.com, used for a status page. See Branding & custom domains.

D#

Degraded. A monitor state shown in amber. The monitor answered but was slower than its Degraded above (ms) threshold, or a failure isn't confirmed yet. Degraded doesn't open an incident.

Deployment correlation. Recording your deploys so they appear next to incidents that start around the same time. See Deployment correlation.

DNS monitor. A monitor that looks up DNS records and alerts when they change or stop matching the values you expect. See DNS.

Down. A monitor state meaning a confirmed incident is open.

E#

Error budget. How much unreliability an SLO allows over its time window. See Reliability insights.

Escalation policy. A sequence of notification steps that runs until someone acknowledges the incident. See Escalation & on-call.

F#

Failure threshold. How many failed checks in a row a region needs before it counts as down (1–10).

Forbidden keywords. Text that must not appear in a response. Used to catch error pages served with a success status.

G#

Grace period. For heartbeat monitors, the extra time allowed after a job's expected run before it counts as missed.

Group. A named set of monitors, shown as a tab on the Monitors page. Groups can have their own alert emails. See Monitor settings & groups.

Guided preset. A starting template in the new-monitor form, such as Website HTML or JSON API, that fills in sensible check settings.

H#

Health score. A per-monitor reliability score shown in Reliability IQ.

Heartbeat monitor. A monitor for scheduled jobs. The job calls a unique SutramX URL each time it runs, and a late or missing call is a failure. See Heartbeat & cron.

HTTP monitor. A monitor that requests a URL and checks the status code, timing and, optionally, keywords. See HTTP & keyword monitors.

I#

Incident. A confirmed outage of one monitor, from when the failure is confirmed until recovery. See Incidents.

Integration. A connection to an outside service, such as a chat app, an incident tool or a deploy source. Managed in Alerts → Channels & API.

K#

Keyword monitoring. Checking that a response contains a Required keyword or doesn't contain Forbidden keywords.

M#

Maintenance window. A scheduled period of planned work during which down alerts are held back and uptime isn't counted. See Maintenance windows.

Member. The standard team role, for people who work with monitors, incidents and status pages. See Team members & roles.

Monitor. One thing SutramX watches, such as a URL, host, port, DNS name or job, plus the rules for judging it. See Monitors overview.

MTBF. Mean time between failures: the average time between incidents.

Multi-step API check. A monitor that runs several API requests in sequence, passing values from one step to the next. See API & multi-step checks.

N#

Note. A comment on an incident. Public notes are also shown on your status pages.

O#

On-call schedule. A rotation that decides who is on call at any time, used by escalation policies. See Escalation & on-call.

Owner. The single workspace role that manages members, billing, API keys, alert channels and workspace deletion.

P#

Paused. A monitor state meaning checks are stopped. You paused the monitor, or your plan paused it after a downgrade.

Pending. A monitor state meaning there are no check results yet.

Plan. Your subscription level: Free, Starter, Growth or Pro. The plan sets limits and which features you can use. See Plans & limits.

Postmortem. A written review of a resolved incident, stored on the incident page.

Probe region. A location SutramX runs checks from. See Regions & confirmation.

Q#

Quiet hours. A scheduled period when notifications are suppressed. Set it in Alerts → On-call & escalation → Quiet Hours & Deployment Windows.

Quorum. The number of probe regions that must report a monitor down at the same time before an incident opens. It depends on your plan.

R#

Recovery threshold. How many passing checks in a row are needed before an incident resolves (1–10).

Reliability IQ. The dashboard area for SLOs, tail latency, anomalies, dependencies and health scores. See Reliability insights.

Routing. The setting that decides which monitors or groups send alerts to a connected channel. The default is All monitors.

Runbook. Response instructions attached to incidents of matching monitors.

S#

SLO. Service level objective: a reliability target, such as 99.9% availability, tracked with an error budget.

Snooze. Pausing alerts for an open incident for a set time.

SSL & domain expiry reminders. Email and channel warnings before a certificate or domain registration expires, available on HTTP and API monitors. See SSL & domain expiry.

Status page. A web page showing your services' current status, uptime history, incidents and maintenance to your users. See Status pages overview.

Subscriber. A visitor who signed up by email for updates from a status page. See Subscribers & updates.

T#

Tag. A free-text label on a monitor, used for filtering and bulk actions.

Third-party status. Following the official status pages of services you depend on, with alerts for their incidents. See Third-party status.

U#

Up. A monitor state meaning the latest check passed.

Uptime. The share of a monitor's checks that passed over a period. On a monitor's page, paused time and maintenance windows aren't counted. See Uptime math.

W#

Webhook. An alert channel that sends a signed HTTP POST to your own endpoint. See Webhooks.

Website health. Scheduled crawls that find broken links and resources, plus Lighthouse scores. See Website health.

White-label. Removing SutramX branding from a status page, available on Pro.

Workspace. The shared space that holds monitors, incidents, status pages, settings, the team and the subscription. See Workspaces.