Skip to main content

Core Concepts

Projects​

A project is the top-level organizational unit. Each project has its own set of monitors, alerts, incidents, and status pages. Projects are isolated from each other.

Every project has an API key (prefixed km_...) used to authenticate API requests scoped to that project.

Monitors​

A monitor defines a check that Kamustatus runs on a schedule. Each monitor has:

  • Type -- HTTP, TCP, DNS, Ping, or Heartbeat.
  • Target -- the URL, hostname, or endpoint to check.
  • Interval -- how often the check runs.
  • Regions -- which geographic regions run the check.
  • Assertions -- conditions that determine success or failure (e.g. expected status code, response body content).

Check Results​

Every time a monitor runs, a check result is recorded with:

  • Status -- up or down.
  • Response time -- how long the check took in milliseconds.
  • Region -- which region executed the check.
  • Timestamp -- when the check ran.
  • Error details -- if the check failed, what went wrong.

Regions​

Kamustatus runs checks from multiple geographic regions. Running checks from several regions helps distinguish between a localized network issue and a genuine outage. A monitor is considered down only when multiple regions agree.

Alerts​

Alerts notify you when something goes wrong. An alert configuration consists of:

  • Alert rules -- conditions that trigger the alert (e.g. monitor goes down, SSL certificate expiring).
  • Notification channels -- where the alert is sent (Slack, email, webhook, etc.). Kamustatus supports 14 channel types.
  • Alert history -- a log of all alerts that have been triggered.

Incidents​

When a monitor detects a failure, an incident is automatically created. Incidents have:

  • Status -- investigating, identified, monitoring, resolved.
  • Updates -- a timeline of status changes and notes.
  • Affected monitors -- which monitors are involved.

You can also create maintenance windows to schedule planned downtime without triggering alerts.

Status Pages​

Public status pages show the current and historical uptime of your services. They are accessible at https://app.kamustatus.com/status/<slug> or via a custom domain using a CNAME record.