Skip to content
Docs

Monitor your first website

On this page
  1. 1. Create your account
  2. 2. Decide who gets alerted
  3. 3. Create the sensor
  4. 4. Watch the first results
  5. 5. What happens when it fails
  6. Where to go next

In a few minutes, you will have a sensor checking your website every few minutes and a notification channel ready to warn you. Everything here works on the Free plan, with nothing to install.

1. Create your account#

Sign up at app.onagre.io/register with your name, your work e-mail, a password and the name of your organization (your workspace — you can rename it later). Confirm your e-mail address with the link you receive, then sign in.

Your organization starts with:

  • the Free plan (up to 10 sensors, checked every 5 minutes at most);
  • a default service, General, and a default environment, Default;
  • an e-mail integration for you, so you can be alerted by e-mail straight away.

2. Decide who gets alerted#

Onagre notifies the integrations you link to each sensor. Your own e-mail is already there. To alert a team channel as well, open Integrations → Add integration and pick Slack or Discord (Google Chat, Microsoft Teams, Webhook, Pushover and Gotify come with paid plans). Each one needs only a name and a webhook URL — see Integrations.

3. Create the sensor#

Click New monitor, choose Configure manually, and follow the wizard (the Website availability template, under Start from a template, gets you to step 3 directly):

  1. What to monitor — choose Website.
  2. Strategy — choose Website availability to check that the site answers, or Specific content to also check that a word appears in the page.
  3. Configuration — give the sensor a name (Corporate website), paste the URL, keep the Onagre public agent, and under Alerting select your e-mail and your Slack channel.
  4. Review — check the summary and click Create monitor.
Configuring manually: pick a goal, a check, fill in the target, choose the agent and who gets alerted, review, create.

The defaults are sensible: a HEAD request, a timeout, HTTP codes 2xx and 3xx accepted, SSL certificate verified. You can change any of them later with Edit.

4. Watch the first results#

You land on the sensor's page. It shows Pending until the first check runs, then Operational — or Down if the site does not answer as expected. Uptime, response times and a chart fill up as checks accumulate. See Results and history.

5. What happens when it fails#

If a check fails, Onagre opens an incident at once and notifies the integrations you selected. Open it from the notification or from Incidents, and click Acknowledge to tell your team you are on it. When the site answers again, the incident is resolved automatically and a recovery notification is sent.

Where to go next#