Skip to content

Quick Start

This guide walks you through setting up CheckOps from sign-up to your first alert.

Navigate to checkops.eu and sign up using:

  • Email + password
  • GitHub OAuth
  • GitLab OAuth

All authentication is handled through a dedicated Keycloak realm isolated from other ClearCloud services.

After signing in, you will be prompted to create an organization. Organizations are the top-level container for all your monitors, integrations, and team members.

Organization name: Acme Corp
Slug: acme-corp (auto-generated, must be unique)

You can invite team members later from the Members settings page.

From the dashboard, click Add Monitor and configure:

Field Example Notes
Name Production API Descriptive label
URL https://api.acme.com/health Full URL with protocol
Type HTTP/HTTPS Also supports TCP and Ping
Interval 60s Check frequency (30s minimum on PRO)
Regions Paris, Frankfurt Select from available EU regions

Add one or more assertions to define what “healthy” means:

- type: status_code
operator: equals
value: 200
- type: response_time
operator: less_than
value: 2000 # milliseconds
- type: body
operator: contains
value: '"status":"ok"'

The dashboard shows all monitors in a dense, terminal-style layout:

  • Green — All assertions passing
  • Amber — SSL certificate expiring soon or degraded performance
  • Red — Monitor down or assertion failing

Each monitor card shows current status, uptime percentage, average response time, and last check timestamp.

Navigate to Integrations to configure alert channels:

  • Webhooks — POST notifications to any endpoint
  • Slack — Channel notifications via webhook URL
  • PagerDuty / OpsGenie — Incident management integration

Alerts fire when a monitor transitions between UP, DEGRADED, and DOWN states. You can configure alert thresholds per monitor.