Monitors Overview

Monitors are checks that run on your schedule and write a status + latency sample. Use this page to pick the right monitor type and understand status behavior.

Status values

Kener monitor results can be:

UP: Check succeeded
DEGRADED: Check succeeded but is unhealthy by your logic/threshold
DOWN: Check failed
MAINTENANCE: Overridden by an active maintenance window
NO_DATA: No signal yet (mainly used by heartbeat monitors before first ping)

Status priority

Final status is resolved by priority:

MAINTENANCE > INCIDENT > REALTIME > DEFAULT

So realtime checks do not override an active maintenance or incident state.

Scheduling

Monitors run from cron expressions (for example * * * * * for every minute). Use tighter schedules for critical services and relaxed schedules for low-risk dependencies.

Uptime calculation

Default uptime formula:

      UP + MAINTENANCE
-------------------------------- x 100
UP + MAINTENANCE + DEGRADED + DOWN

Monitor types

API Monitor — HTTP/HTTPS checks with custom eval logic
Ping Monitor — ICMP reachability/latency for hosts
TCP Monitor — TCP port open/timeout/error checks
DNS Monitor — DNS record matching (ANY/ALL)
SSL Monitor — TLS certificate expiry thresholds
SQL Monitor — Run SQL query against DB connection
Heartbeat Monitor — Push-based health signal
GameDig Monitor — Game server query checks
gRPC Monitor — gRPC Health Checking Protocol
Docker Monitor — Container state and healthcheck via the Docker Engine API, or the daemon itself
Group Monitor — Weighted aggregate of member monitors
Prometheus Monitor — PromQL instant query with threshold-based status

Stored secrets

The dashboard and the REST API show these stored values as ********: each header value, the request body, the proxy URL, a SQL connectionString, a Docker tlsKey, and a heartbeat secretString. Monitor checks use the real values.

The dashboard shows the heartbeat secret to users with monitors.write, so they can copy the heartbeat URL.
A save that sends ******** back keeps the stored value. To change a secret, type the new value.
A $SECRET reference such as Bearer $API_TOKEN is masked too. The value stays in the environment variable.

Grace Period — require N consecutive checks before a status change is recorded
Monitors (general)
Sharing Monitors
Alert Configurations