New to this? You're in the right place. This post doesn't assume you know what "uptime" means, or what it takes for a website to actually be "monitored." If a word needs explaining, it's explained right where it shows up.
The problem this kind of software solves
A website is either working or it isn't. Most of the time nobody's watching closely enough to notice the moment it breaks — a page starts returning an error, or it just gets slow — until a customer emails to complain. By then it might have been broken for hours.
"Monitoring" is just keeping an organized record of a site's health over time: is it up, how fast is it responding, and — separately — how many people are actually visiting and what are they doing when a visitor sends a message through the contact form. Three different kinds of information, all worth tracking somewhere that isn't just someone's memory.
The two words you'll see everywhere
- Uptime is simply how much of the time a website is actually working and reachable. If a site is up 99% of the time in a month, that's about seven hours it wasn't.
- An outage is one specific stretch where the site wasn't working — however short or long. Each one gets its own tracked entry, not just a vague memory of "it went down once."
What this actually watches — and what it doesn't
Here's the part worth being direct about, because "monitoring tool" can sound like something that's constantly checking your site on its own: out of the box, this doesn't check anything by itself. It's a place to record what happened — an outage, a traffic count, a contact-form message — after something else tells it, whether that's you typing it in by hand or a connection you've set up sending it automatically.
Only one of the three kinds of information here fills itself in automatically without extra setup: a contact-form submission, if you've pointed your site's contact form at this system. The other two — outages and traffic numbers — arrive either because you enter them yourself or because you've connected your own separate uptime checker or analytics tool to feed them in. Nothing here is quietly watching your site behind the scenes unless you've deliberately wired it up to.
What you'd actually see, in a project
If you opened a project built from a "Site Monitoring" starting template, you'd find three separate lists (queues), each doing one job:
| What you'd see | What it's for, in plain words |
|---|---|
| An incidents list | One entry per outage or slowdown — when it started, how bad it was, when it got fixed |
| A traffic snapshots list | One entry per time period — how many visits, how many different visitors, where they came from |
| A form submissions list | One entry per message someone sent through the site's contact form |
Two dashboards (screens) show the big picture at a glance: one for site health — what's currently broken, what's been fixed — and one for traffic and incoming messages.
What this isn't (yet)
An honest note, because overselling doesn't help anyone: this isn't a service that pings your website every few minutes and alerts you the moment it goes down. It's a record-keeping system. If you want that kind of active checking, you'd point a separate uptime-checking tool at your site and feed its results in here — or just log outages by hand when you notice them, which is a perfectly reasonable way to start.
Ready for the deeper version?
Everything above describes the shape of the Site Monitoring template built into OpenTechnologyApp. If you want the real technical detail — the exact automations, every field, which of the three lists actually fills itself in — the full version is here: Site Monitoring: A Free-Tier Template for Outages, Traffic, and Contact Forms.
If this was your first time reading about website monitoring, you now know enough to follow that post — and enough to tell whether this kind of tool would actually help you.