Monitors Overview

Monitors are the foundation of YipYap. Each monitor runs a specific type of check against a service endpoint on a recurring schedule and tracks whether that service is healthy.

Monitor Types

Type	What It Checks
HTTP	URL reachability, status codes, response body
TCP	Port connectivity and optional TLS handshake
DNS	DNS record resolution and expected values
Ping	ICMP reachability and round-trip latency
Heartbeat	Receives pings from your service on a schedule

Common Settings

Every monitor shares these configuration options:

• Name: A human-readable label for the monitor.
• Check Interval: How often the check runs (30s, 60s, 5m, etc.).
• Timeout: Maximum time to wait for a response before marking the check as failed.
• Latency Warning Threshold: Latency in ms that triggers a degraded state.
• Latency Critical Threshold: Latency in ms that triggers a critical alert.
• Down Severity: Alert severity when the monitor goes down (warning or critical).
• Degraded Severity: Alert severity when the monitor is degraded.
• Escalation Policy: Which policy to trigger when the monitor enters the Down state.
• Runbook URL: Link to the runbook for this monitor (shown in notifications).

Status States

A monitor is always in one of three built-in states:

State	Meaning
Up	All checks are passing.
Down	The confirmation threshold has been reached.
Degraded	The check is failing intermittently but has not confirmed down.

Beyond these built-in states, you can define custom monitor states for your organization. Each custom state has a name, health class (healthy, degraded, or unhealthy), severity, and color. See Custom Monitor States for details.

Match Rules

Match rules let you map specific HTTP response conditions to custom states on a per-monitor basis. Each rule evaluates conditions such as status code (exact or range), body content (contains, regex), or response headers. Rules are ordered, and the first matching rule wins.

Configure match rules in the monitor edit form under the Match Rules section.

Monitor Tags

Tags are key-value labels you can attach to any monitor for filtering and organizing. Add tags in the monitor creation or edit form. Once applied, use the tag bar on the monitor list page to filter monitors by tag.

Auto-Resolve

When auto-resolve is enabled on a monitor, any alert triggered by that monitor will automatically resolve when the monitor recovers to a healthy state. This is disabled by default and can be toggled per monitor.

Monitor Description

Each monitor supports an optional free-text description field. The description is displayed on the monitor detail page and can be used to document what the monitor checks, who owns it, or any relevant context.

Monitor Groups

You can group related monitors together for a composite rollup status view. The group’s status reflects the worst status among its child monitors. See Monitor Groups for details.

Setup Guide

1. Navigate to Monitors in the sidebar.
2. Click New Monitor and select a monitor type (HTTP, TCP, DNS, Ping, or Heartbeat).
3. Fill in the type-specific fields (URL, hostname, port, etc.).
4. Configure the check interval, timeout, and latency thresholds.
5. Assign an escalation policy to define who gets notified on failure.
6. Click Save to activate the monitor.

Tip

Set latency thresholds to catch degradation before a full outage. For example, warning at 500ms and critical at 2000ms.

Caution

Monitors with very short intervals (10s) consume more of your plan’s check quota. Use 30s or 60s intervals unless you need near-instant detection.

Rate Limits

The Free plan supports up to 5 monitors with a minimum interval of 60 seconds. Pro supports up to 500 monitors with 30-second intervals. Enterprise supports unlimited monitors with 10-second intervals.