Checks and results
Run endpoint checks, read the recorded evidence, and understand check history.
Stazus records each request as a check. A check gives you the evidence needed to decide whether an endpoint is healthy.
Run a manual check
- Open an endpoint.
- Select Run check.
- Read the result card.
- Open the check history or related incident when you need more context.
The result card shows whether the request passed. It also shows the HTTP status, time to first byte, total duration, and failure reason when present.
Understand check sources
| Source | Meaning |
|---|---|
| Scheduled | Stazus ran the check from the endpoint schedule. |
| Manual | A user selected Run check or the alert action. |
The primary Run check action creates a diagnostic record. It does not change uptime statistics. It does not affect incidents.
The adjacent alert action runs a check and evaluates alert signals. Use it only when you want the manual result to participate in incident handling.
Read a check result
Check records can include these values:
| Field | Meaning |
|---|---|
| Success | The check met the configured response expectations. |
| Status code | The HTTP response status. 0 means that the request did not complete. |
| Time to first byte | Time until Stazus received the first response byte. |
| Duration | Total time for the request. |
| Failure reason | The reason reported for a failed check. |
| Response excerpt | A limited response excerpt when Stazus recorded one. |
| Body complete | Whether Stazus received the complete response body. |
| Latency anomaly | Whether latency crossed the active threshold. |
| Alerts suppressed | Whether the check was excluded from alert handling. |
Read live state
The endpoint page shows the latest check independently from the selected statistics window.
- Operational means that the latest check passed.
- Down means that the latest check failed.
- Never checked means that Stazus has no check result yet.
When an endpoint is down, the page also shows consecutive failures.
Use statistics carefully
Endpoint and project views show checks, failures, uptime, average latency, and p95 latency for the selected time window. If Stazus has no successful checks, latency values have no data.
Maintenance-window checks and manual diagnostics do not affect uptime statistics.
Investigate a failure
- Read the failure reason and status code.
- Compare the newest check with the last healthy result.
- Check the response excerpt when Stazus recorded one.
- Review latency and alert state.
- Open or update an incident when the failure needs coordinated response.
See incidents for the response workflow.
Last updated on