Stazus docs
Stazus docs

Introduction

Stazus documentationGet startedConcepts

Planned features

Feature availabilityStatus pages

Monitoring

MonitorsChecks and resultsLatency alertingMaintenance windows

Incident response

IncidentsNotificationsTeams and access

Developer API

Developer APIAuthenticationProjectsEndpointsAnalyticsIncidentsErrors and limitsMigrate from v1

Account and help

Account and security

Help

Support

Updates

Changelog
Changelog launchedDocumentation UpdatesDeveloper API v2Scope-aware maintenance windows

Latency alerting

Configure latency detection, learn the alert states, and avoid false incidents.

Latency detection evaluates slow responses separately from availability failures. Configure it when response speed is an operational requirement.

Choose a detection mode

ModeBehaviour
OffStazus measures latency but does not classify anomalies or open latency incidents.
ShadowStazus classifies anomalies for review but does not open incidents.
AutomaticStazus learns a baseline from recent checks and evaluates anomalies against it.
FixedStazus evaluates latency against the fixed threshold that you set.

Start with shadow mode

  1. Create or edit an endpoint.
  2. Select Shadow as the latency detection mode.
  3. Save the endpoint.
  4. Review the endpoint Alerting panel after representative checks run.
  5. Select Automatic or Fixed when the results match your operational expectations.

Shadow mode reduces the risk of alert noise while you learn normal performance.

Configure automatic mode

Automatic mode learns a baseline. The Alerting panel shows its sample count, median, p95, open threshold, and recovery threshold.

Set these values:

SettingLimit or meaning
SensitivityA number from 1 to 20.
Minimum learning samplesAn integer from 20 to 10,000.
Trigger breachesThe number of breaches needed to trigger. It cannot exceed the trigger window.
Trigger windowThe number of checks examined for breaches. It is 1 to 20.
Recovery streakThe number of healthy checks needed for recovery. It is 1 to 20.
Fixed thresholdAn optional safety ceiling during automatic mode.

Stazus shows Warming up until it has the required number of samples. If no learned baseline exists and you set a fixed threshold, Stazus uses that fixed ceiling.

Configure fixed mode

  1. Edit the endpoint.
  2. Select Fixed threshold.
  3. Enter a threshold in milliseconds.
  4. Set the trigger and recovery values.
  5. Save the endpoint.

The fixed threshold is required in fixed mode. It must be at least 1 millisecond.

Read alert states

The Alerting panel can show these signal states:

StateMeaning
NormalStazus has no active signal.
SuspectedStazus observed a recent breach but did not open an incident.
FiringStazus has an active incident for the signal.
RecoveringThe active signal has a recovery streak.

Use the panel with check history. A latency anomaly does not always prove that users experienced an outage.

Related guides

  • Configure monitors
  • Read checks and results
  • Investigate incidents

Last updated on

Checks and results

Run endpoint checks, read the recorded evidence, and understand check history.

Maintenance windows

Keep checks running while you suppress automatic incidents during planned work.

On this page

Choose a detection modeStart with shadow modeConfigure automatic modeConfigure fixed modeRead alert statesRelated guides