Add your first site, alert and status page
Add a site, get a first alert through the default email notification and publish a status page, using the app's own labels.
Last reviewed
On this page
This page takes one site from nothing to a first check, a first alert and a public status page. It uses the app's own labels, so you can follow it with the app open.
Before you start
You need an account with a verified email address. You can sign in before you verify, but the app refuses to add a site until the address is verified, with the message Please verify your email address before adding a monitor. Use the link in the verification email.
1. Add a site
Open Websites and choose Add Website
The form opens with the defaults described below.
Enter the Website URL
Use the full URL including
https://orhttp://. A site is one URL, so enter the page you want watched. The same URL can't be added twice to one workspace, and a second attempt is refused withThis website is already being monitored in your workspace.Pick a Group (optional)
A group organizes sites, for example one group per client. You can change it later.
Review the checks and save
Uptime is always on and runs every 5 minutes by default. SSL Certificate Expiration and WHOIS Registration start on. The other checks start off. Expand a check to change its interval or switch it on.
OctoPing starts the first round of checks as soon as the site is saved, so you don't wait for the first scheduled interval. Until the first result arrives, the site shows Pending. It then reads Online, Degraded or Offline. The statuses page defines each of them.
| Setting | Starts as |
|---|---|
| Uptime interval | Every 5 minutes |
| SSL certificate | On, checked every day |
| WHOIS registration | On, checked every week |
| DNS (MX and nameservers), content, robots.txt, IP and hosting | Off |
2. Get your first alert
Adding a site also creates a notification named Default Email Notification. It emails the members of the workspace at the moment the site is added. It waits for 3 consecutive failed checks before it sends a down alert, repeats at most every 10 minutes while the site stays down, and sends a recovery message when the site comes back. With checks every 5 minutes, the last of those failed checks comes about 10 minutes after the first. The probe regions get up to 10 minutes from the first failure to confirm it, so with the defaults the down alert goes out with that last failed check. The vantage points page explains how that works.
Open the site and choose Notifications
The Notification Management page lists every notification on the site.
Send a test
Choose Send Test on a notification. OctoPing sends a test message through that channel immediately and shows the result on the page.
Add another channel (optional)
Choose Add Notification and pick a Notification Type. The channels are Email, Slack, Discord, Webhook and Browser push.
Check the log
View Logs shows every attempt as sent, failed or skipped, with the reason for a skipped one.
3. Publish a status page
Open Status Pages and choose Create Status Page
Enter a Name (it labels the page in the app and is shown as the name field in the page's public JSON), a URL Slug, a Page Title and an optional Description and Company Website URL. The slug becomes the page address, and it must be unique across all of OctoPing.
Add items
In Monitored Items, choose Add Item and pick a website or heartbeat. Only the items you add appear on the page, and each item can be hidden without removing it.
Preview
Choose Preview to see the page before anyone else can.
Switch it to Published
A new page is a Draft and answers with a 404 to the public. Turning on the Published switch makes it live at
/status/your-slugon the OctoPing domain.
The public page shows each item's current status and 90 days of daily history for sites and 90-day uptime for heartbeats. The public status words are listed on the statuses page.
Where to go next
The checks reference covers what each check measures and how to tune it. The vantage points page explains why a down alert can wait a few minutes for the regional probes to agree.
Related
- DocsGetting started with OctoPingWhat OctoPing monitors, how alerts and status pages fit together, and the terms the rest of the documentation uses.
- DocsStatusesThe statuses a site and a heartbeat can have in the app and on a public status page, and the order in which the rules apply.
- DocsVantage points and confirmationHow the primary checker and the probe regions confirm a failure, what Partial means and why OctoPing alerts when the probes are silent.