Concepts
Learn the records and states that Stazus uses for monitoring and incident response.
Use these terms consistently when you configure or investigate Stazus.
Team
A team is a workspace. It owns projects, incidents, notifications, members, and settings. Each member has one role in each team.
Project
A project groups endpoints that one group owns. Use a project for one product, service boundary, or operational area. Projects also define a subscription scope.
Endpoint
An endpoint is one HTTP monitor. It stores the request, expected response, schedule, latency settings, and optional maintenance time. An endpoint can be enabled or disabled.
Maintenance window
A maintenance window covers the whole team, one project, or one endpoint for a defined period. Covered checks continue to run, but they do not affect automatic incidents or monitoring analytics.
Check
A check is one recorded request to an endpoint. Scheduled checks run at the configured interval. Manual checks run when a user chooses Run now.
Each check can include these values:
- Success or failure
- HTTP status code
- Time to first byte
- Total duration
- Response excerpt, when available
- Failure reason, when present
- Latency anomaly state
- Alert suppression state
Incident
An incident records an operational event. Stazus can create an incident from a monitor signal. Editors can also create an incident manually.
An incident can affect one or more endpoints. It has a type, severity, workflow status, comments, checkpoints, and check evidence.
Notification
A notification is an in-app record for an incident or system event. You can filter the notification list, mark items as read, or mark all items as read.
Email contact methods receive alert delivery when they are verified, enabled, and included by a subscription.
Roles
Teams use two roles:
| Role | Access |
|---|---|
| Editor | Changes team settings, members, subscriptions, monitors, and incident records. |
| Viewer | Reads team information and operational records. |
Related guides
Last updated on