Monitors Overview

Monitors are the core of Hoppla. Each monitor watches a URL or endpoint and runs one or more checks against it on a recurring schedule. When a check detects a problem, Hoppla creates an incident and notifies you through your configured notification channels.

Monitor Types

Hoppla supports three monitor types. The type determines the transport protocol used to reach your endpoint.

Type	Protocol	Description
HTTP	HTTP/HTTPS	Monitors websites and web APIs. This is the most common type and supports the widest range of check types -- from uptime and SSL to Lighthouse audits and broken link detection.
Ping	ICMP	Monitors host reachability using ICMP echo requests. Useful for servers and network devices that do not serve HTTP.
TCP	TCP	Monitors arbitrary TCP port connectivity. Useful for databases, mail servers, game servers, and other non-HTTP services.

Check Types

Each monitor can have multiple checks enabled simultaneously. Checks are grouped into two categories.

Availability Checks

Availability checks represent actual site uptime and reachability. Only these check types create incidents on public status pages.

Check	Description	Page
Uptime	HTTP/HTTPS availability with dual-check verification	Uptime
SSL Certificates	Certificate expiry, chain validity, protocol versions	SSL
DNS Records	Record + nameserver change detection for A, AAAA, CNAME, MX, TXT, NS, SOA, SRV, CAA	DNS
Application Health	Custom health endpoint monitoring	Application Health
TCP Port	TCP port connectivity checks	TCP
Ping (ICMP)	ICMP echo-based reachability	Ping

Advisory Checks

Advisory checks are informational quality metrics. They produce warnings but never create incidents -- their maximum status is warning.

Check	Description	Page
Lighthouse Audits	Performance, accessibility, SEO, and best-practice scores (lab data)	Lighthouse
Core Web Vitals	Real-user performance from Chrome telemetry (LCP, INP, CLS)	Core Web Vitals
GEO (AI Readiness)	How discoverable and quotable your site is for AI assistants	GEO
Broken Links	Crawls your site to find 404s, 5xx errors, and timeouts	Broken Links
Security Headers	Checks for recommended HTTP security headers	Security Headers
Mixed Content	Detects insecure HTTP resources loaded on HTTPS pages	Mixed Content
Redirects	Analyzes redirect chains for issues	Redirects
Sitemap	Validates your XML sitemap	Sitemap
Robots.txt	Checks robots.txt for correctness	Robots.txt
DNSBL (Blacklists)	Checks if your IP is listed on DNS blacklists	DNSBL
Domain Expiry	Monitors domain registration expiry dates	Domain Expiry

Adding a Monitor

1. Navigate to Monitors in the dashboard sidebar.
2. Click Add Monitor.
3. Enter a name and URL for your monitor.
4. Select the monitor type (HTTP, Ping, or TCP).
5. Configure the check interval and enable the checks you want to run.
6. Save the monitor.

Hoppla begins running checks immediately after the monitor is created. For a step-by-step walkthrough, see Your First Monitor.

Monitor Settings

Check Interval

The check interval controls how often Hoppla runs checks against your monitor. Each check type runs on its own schedule with its own sensible default. Fast availability checks (uptime, ping, TCP) can run as often as every 30 seconds, while resource-intensive advisory checks (Lighthouse, GEO, broken links, Core Web Vitals) run no more often than every 6 hours. The longest interval is 24 hours. The fastest interval available to you depends on your plan.

Typical defaults: uptime 60s, TCP 60s, ping 60s, application health 5 minutes, SSL 3 hours, security headers 6 hours, mixed content 6 hours, DNS 12 hours, robots.txt 12 hours, redirects 12 hours, domain expiry 24 hours, DNSBL 24 hours, sitemap 24 hours, Lighthouse 24 hours, Core Web Vitals 24 hours, GEO 24 hours, broken links 24 hours.

Enabled Checks

Each monitor can have multiple checks enabled at the same time. For example, an HTTP monitor might have uptime, SSL, DNS, and security headers checks all running on their own schedules. Enable or disable individual checks from the monitor detail page.

Notification Preferences

Per-monitor notification settings let you control:

• Mute notifications -- Temporarily suppress all alerts for a monitor.
• Confirmation threshold -- How many consecutive failures are required before an incident is created (default: 1).
• Recovery threshold -- How many consecutive successes are required before an incident is auto-resolved (default: 1).
• Cooldown period -- Minimum time between repeated notifications for the same check.
• Warning notifications -- Whether advisory check warnings (SSL expiring, security headers, etc.) are sent.
• DNS change notifications -- Whether DNS record changes trigger notifications.

Tags

Tags let you organize monitors into groups. Use them to filter the monitor list, scope status pages, or group related services together. Each monitor supports up to 20 tags.

Pause / Maintenance

You can pause a monitor temporarily by setting a paused until date. Hoppla will stop running checks for that monitor until the pause expires. For planned downtime, use Maintenance Windows instead -- they suppress alerting without pausing checks.