Stector is uptime monitoring and status pages in one product. It checks your HTTP endpoints, your SSL certificates' expiry dates and your domains' registration expiry dates from outside, alerts you when a monitor goes down, 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 one or more regions, and opens an incident when a monitor goes down. While a maintenance window that lists a monitor is in progress, Stector holds back that monitor's down and recovery alerts and opens no incident for it automatically. 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, an SSL certificate check or a domain expiry check. HTTP and SSL monitors run on a schedule from one or more regions. HTTP monitors verify a URL returns the status code you expect. SSL monitors check a certificate's expiry date; expiry warnings are off until you set how many days ahead to be warned (see SSL monitoring). Domain expiry monitors read a domain's registration expiry date once a day and warn you before it lapses; they show Down once it has expired but never open an incident, and they work only for TLDs whose registry publishes an RDAP service (see Domain expiry monitoring).
Incidents. When a monitor goes down, Stector opens an incident automatically (see Monitoring HTTP endpoints for when that happens, and Maintenance windows for the exception). Incidents are recorded before notifications go out, so a failed email or Slack message doesn't change the incident.
Alert channels. Alert channels are where notifications go when a monitor's status changes. Stector supports email, and Slack and webhooks on the Pro and Business plans. 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. A team can have several, depending on its plan.
Continue to Create your first monitor to set up your first check.