HopplaKnowledge Base

Everything you need to know about monitoring your websites, servers, and scheduled tasks.

Getting Started
Reseller / Hoster Docs

Monitors

Uptime, SSL, DNS, domain expiry, and 13 more check types — all from one dashboard.

Alerting

Email, Slack, Discord, Teams, PagerDuty, Telegram, and webhooks. Know the moment something goes wrong.

Cron Monitors

Heartbeat monitoring for your scheduled tasks. Get alerted when a job doesn't run.

Agent Monitors

Lightweight server agents that report CPU, memory, disk, and custom metrics.

Status Pages

Public and branded status pages for your customers. Custom domains supported.

API & AI (MCP)

Full REST API for automation, plus a built-in MCP server so AI assistants can read your monitoring data.

Start here ​

  • Quickstart — from signup to a watched URL.
  • Understanding checks — monitors and checks are two different things, and the difference decides how you configure everything else.
  • Notification channels — where alerts land: email, Slack, Discord, Telegram, Microsoft Teams, PagerDuty or a webhook.
  • Self-hosting — run the whole platform on your own infrastructure.

What a monitor checks ​

A monitor is one URL or host. Each monitor runs as many checks as you enable, each on its own schedule and with its own history. Checks come in two kinds:

  • Availability checks decide whether your site counts as up. A failure opens an incident, updates your status page and triggers notifications.
  • Advisory checks report quality problems. They raise warnings in the dashboard, but never open an incident and never change your reported availability.

Uptime failures are re-tested from a second, independent probe location before an incident is created. A blip between one probe and your server will not wake anyone up.

CheckKindWhat it catches
UptimeAvailabilityThe site is unreachable or returns an error status
SSL certificatesAvailabilityCertificate expiring, broken chain, wrong domain
DNS recordsAvailabilityA record changed, or authoritative nameservers moved
Application healthAvailabilityYour own health endpoint reports a degraded component
TCP portAvailabilityA database, mail or game server stopped accepting connections
Ping (ICMP)AvailabilityA host is unreachable at the network level
Domain expiryAdvisoryThe domain registration is running out
LighthouseAdvisoryPerformance, accessibility, SEO or best-practice scores dropped
Core Web VitalsAdvisoryReal visitors are seeing slow loads or layout shifts
GEO auditAdvisoryAI assistants cannot read, understand or cite your pages
Broken linksAdvisoryLinks on your site lead to 404s, 5xx errors or timeouts
Security headersAdvisoryCSP, HSTS or other protective headers are missing or weak
Mixed contentAdvisoryHTTPS pages load resources over plain HTTP
RedirectsAdvisoryRedirect loops or chains that cost visitors time
SitemapAdvisoryThe XML sitemap is unreachable or lists broken URLs
robots.txtAdvisoryCrawler rules changed, or a bot policy blocks something it should not
DNSBLAdvisoryYour domain or IP landed on a spam blacklist

Scheduled jobs and servers are watched differently. A cron monitor waits for a heartbeat ping from your task and alerts when it does not arrive within the grace period. An agent monitor runs a small agent on your server and reports CPU, memory, disk and load.

Glossary ​

Monitor
One URL or host you want watched. The top-level object you create in the dashboard.
Check
One test run against a monitor, such as uptime or SSL. A monitor can run many checks at once, each with its own schedule, status and result history.
Probe location
The region a check runs from. Uptime failures are confirmed from a second location before an incident opens.
Incident
An open problem on a monitor, created when an availability check fails. It drives status pages, notifications and escalation.
Heartbeat
A ping your scheduled task sends to a unique URL after it runs. Silence, rather than an error, is what triggers the alert.
Grace period
How long a cron monitor waits past the expected run time before it treats a missing heartbeat as a failure.

Frequently asked questions ​

What is the difference between a monitor and a check?

A monitor is what you watch: one URL or host. A check is how it gets watched: uptime, SSL, DNS and so on. One monitor runs many checks, and each check keeps its own schedule, status and history. See Understanding checks.

Will a single network blip page me at 3am?

No. When an uptime check fails, Hoppla immediately re-runs it from a second, independent probe location. An incident is only created when both locations agree the site is down.

Which checks affect my uptime percentage?

Only availability checks: uptime, SSL certificates, DNS records, application health, TCP port, ICMP ping, and cron or agent heartbeats. Advisory checks such as Lighthouse, broken links and security headers raise warnings without touching your availability figure.

How do I monitor a cron job or a background worker?

Create a cron monitor, set its schedule as a cron expression and a grace period, then have your task request the generated ping URL after each successful run. If the ping does not arrive in time, Hoppla opens an incident.

Can I run Hoppla on my own servers?

Yes. The self-hosted edition runs the same platform on your infrastructure, including white-label branding. Start with installation and configuration.

Is there an API, and can AI assistants read my monitoring data?

Both. The REST API covers everything the dashboard does and ships an OpenAPI specification, and the built-in MCP server lets AI assistants query your monitors over Model Context Protocol.