Uptime Monitors

Uptime monitors check your endpoints at regular intervals and can automatically update your status page when issues are detected.

How It Works

Kodo sends HTTP requests to your endpoint at the configured interval
We check for successful responses (2xx status codes by default)
If checks fail, the linked service status is updated
You receive alerts via your configured notification channels

Creating a Monitor

Dashboard
CLI
API

Go to Dashboard > Uptime
Click Add Monitor
Enter the URL to monitor
Configure check interval and alerting
Optionally link to a service

kodo monitors create \
  --name "API Health Check" \
  --url "https://api.example.com/health" \
  --interval 300 \
  --service "API Gateway"

curl -X POST "https://kodostatus.com/api/v1/uptime-monitors" \
  -H "X-API-Key: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "API Health Check",
    "url": "https://api.example.com/health",
    "interval_seconds": 300,
    "service_id": "svc_abc123"
  }'

Check Intervals

Interval	Best For
60 seconds	Critical services requiring fast detection
5 minutes	Standard monitoring
15 minutes	Less critical services
30 minutes	Low-priority endpoints

Monitor Settings

string

required

The endpoint to monitor (must be HTTPS)

integer

default:"200"

Expected HTTP status code

integer

default:"30000"

Request timeout in milliseconds

boolean

default:"true"

Whether to follow HTTP redirects

object

Custom headers to include in requests

Monitoring Regions

Checks are performed from multiple regions to avoid false positives:

US East (Virginia)
US West (Oregon)
Europe (Frankfurt)
Asia Pacific (Singapore)

An endpoint is only marked as down if checks fail from multiple regions.

Incident Safeguards

When a monitor detects failures, Kodo doesn’t immediately create an incident. Instead, it passes through safeguards to prevent false alarms:

Setting	Default	Purpose
Failure threshold	3	Must fail this many times consecutively
Cooldown	15 minutes	Minimum gap between auto-incidents
Severity override	Auto (Major)	Override severity for this monitor’s incidents

Configure these in the Incident Safeguards section when creating or editing a monitor. Auto-created incidents also respect your organization’s draft mode and notification batching settings.

Full Safeguards Reference

Flap protection, draft mode, cooldowns, maintenance awareness, and more.

Automatic Status Updates

When linked to a service, monitors can automatically update status:

Monitor Status	Service Status
Up	Operational
Degraded (slow response)	Degraded
Down	Major Outage

Response Time Tracking

We track response times for all checks:

Average response time
95th percentile
Slowest responses
Response time trends

View these metrics in the dashboard or query via API.

Getting Started

Status Management

Monitoring

Alerting

Automation

Notifications

Client Tracking

Integrations

Uptime Monitors

How It Works

Creating a Monitor

Check Intervals

Monitor Settings

Monitoring Regions

Incident Safeguards

Full Safeguards Reference

Automatic Status Updates

Response Time Tracking

​How It Works

​Creating a Monitor

​Check Intervals

​Monitor Settings

​Monitoring Regions

​Incident Safeguards

Full Safeguards Reference

​Automatic Status Updates

​Response Time Tracking

How It Works

Creating a Monitor

Check Intervals

Monitor Settings

Monitoring Regions

Incident Safeguards

Automatic Status Updates

Response Time Tracking