Docs

Add your first monitor

PulseKeeper checks your sites and servers from several locations around the world, tells you when something is down or getting slow, and shows what changed around it.

1. Add a monitor

Go to Monitors → Add monitor and choose what to watch:

  • Website: a page over HTTPS or HTTP, for example shop.example.com or example.com/login;
  • TCP port: a database, mail server or SSH, for example db.example.com:5432;
  • Ping: a server or device that answers ICMP;
  • API endpoint: a request with your own method, headers and body, with checks on the JSON answer;
  • Cron heartbeat: a job that reports in to us, see cron heartbeats.

Pick a client group if you manage sites for clients, or leave it as No client.

Checks start right away. Until you verify ownership, a new website is checked every 5 minutes from one location.

2. Verify ownership

Verification proves the site is yours and unlocks your plan's full interval and all its locations. It takes a TXT record or one file. See verify ownership. Servers added by IP address or as a TCP port do not need it.

3. Decide who hears about it

Your account starts with one alert channel: the e-mail address you signed up with. Add Slack, Discord, Telegram, SMS or a webhook on the Alerts page. See alert channels.

We write only when something changes state (an outage is confirmed or resolved), never on every check. See how outages are detected.

What each monitor includes

A website monitor takes one slot of your plan and comes with checks that do not take another:

  • SSL certificate: expiry and chain, checked every 6 hours;
  • domain expiry: read from the registry every 12 hours;
  • DNS history: NS, A and MX records every hour (on plans that include it);
  • Google PageSpeed: page load and page weight (on plans that include it).