Help CenterOpen app

Quick Start

The shortest path from a new account to useful monitoring. Use this page for product flow; heartbeat and cron copy-paste snippets live on the Heartbeat page.

1. CREATE THE RIGHT MONITOR

  • Click + and choose the monitor type that matches your signal.
  • For public endpoints, start with HTTP or API.
  • For web apps that need JavaScript, use Browser.
  • For jobs and deploy pipelines, use Heartbeat/Event Receiver.
  • New monitors may start paused depending on how they are created; activate only when you want them spending active capacity.
Top navigation Create monitor button
Start by selecting Create monitor from the top navigation.
Monitor creation workflow showing type, configuration, and schedule sections
Choose a type, configure its target, then set the schedule before creating the monitor.

2. CHECK THE FIRST RESULT

Open the monitor detail page after the first check. Confirm the current state, latency, response status, captured error, and incident timeline. If a monitor is noisy, raise the interval or adjust expected statuses/assertions before wiring alerts.

Monitor header showing current status, target URL, next check countdown and 30-day uptime, downtime and incident counters
The header answers the first question: is it up right now, and how has it behaved over 30 days?
Response breakdown panel with status, DNS, TCP, TLS and TTFB timings beside the activity feed listing a resolved outage
The response panel breaks the last check into DNS, TCP, TLS and TTFB; the activity feed keeps the error text from every past failure.

3. ADD ALERT ROUTING

Go to Settings -> Notifications and configure the channels your team already uses. Then use per-monitor notification overrides if one monitor should page loudly while another only records incidents.

4. SHARE OR EMBED STATUS

  • Use Status Pages for customer-facing or team-facing rollups.
  • Use Embeds for a single monitor card, SVG badge, or JSON status endpoint.
  • Public views are sanitized: URLs, headers, tokens, and private config stay hidden.

5. AUTOMATE THE LOOP

Use Triggers when state changes or payload fields should call another system, open an incident, or send a custom notification. Use API keys when scripts, CI/CD, internal tools, or agents need to create monitors, manage incidents, or read status programmatically.

API status check
curl -fsS \
  -H "Authorization: Bearer $KEEPITALIVE_API_KEY" \
  https://keepitalive.dev/api/v1/status
NextMonitor Types