Stector is a synthetic monitoring and status page tool. It checks whether your endpoints and SSL certificates are healthy, notifies you when something breaks, and gives your customers a public page to check during an incident.
You create monitors for the things you want to watch — an API endpoint, a website, a certificate's expiry date. Stector runs those checks on a schedule from multiple regions, and opens an incident when a check starts failing. You configure alert channels to receive notifications, and connect a status page so your customers see what's going on without filing a support ticket.
The rest of this section walks through the core concepts and gets you to your first working monitor.
Monitors. A monitor is an HTTP check or an SSL certificate check that runs on a schedule from one or more regions. HTTP monitors verify a URL returns the status code you expect; SSL monitors verify a certificate is valid, and can warn you before it expires.
Incidents. When a monitor's checks start failing, Stector opens an incident automatically. The incident record stays accurate even if a notification fails to send — the incident lifecycle and alert delivery are handled separately.
Alert channels. Alert channels are where notifications go when a monitor's status changes. Stector supports email and Slack. An alert policy decides which channels are active; monitors reference a policy to determine who gets notified.
Status pages. A status page is a public page that shows the status of your components and your incident history. Each team has one status page.
Continue to Create your first monitor to set up your first check.