Monitoring

Uptimia ships twelve monitor families, each watching a different thing, so pick the family by what it checks. If two look alike, see Choosing Between Monitor Types . The Twelve Families at a Glance Th

Several of Uptimia's 12 monitor families overlap by name or by job. Pick the wrong one and you get a monitor that stays green through the failure you were worried about. The overlaps that get mixed up

An uptime monitor checks one target on a schedule from the probes you choose, and it opens an incident when enough of them agree the target is failing. The target can be a web URL, a mail server, or a

Your monitor shows green, availability sits at 100%, and customers are emailing you about a broken page. A keyword check closes that gap. It reads the response body and decides up or down on whether s

A heartbeat monitor inverts every other check in Uptimia: instead of a probe reaching your system, your system reaches Uptimia. Your job requests a unique ping URL each time it runs. When a ping does

An API monitor is an ordered chain of up to 15 HTTP requests, and Uptimia replays it on a schedule from your chosen probes: log in, take the token, call the endpoint, check what came back. A failed st

Assertions decide whether a step passed. Extractions pull a value out of one response and hand it to a later step, while monitor variables hold the values that every step in the chain shares. Both kin

A server monitor collects nothing until the Uptimia agent is running on the host. The agent is a script that reads CPU, memory, disk, load and network figures from the operating system, then posts the

A speed monitor loads one URL in a full Chrome browser from your chosen probe locations, and records how long the whole page took: every script, stylesheet, image and font. The same Chrome run records

Real User Monitoring reports what your visitors' own browsers measured: load time, JavaScript errors, and the country, browser, device and operating system each visit came from. A small snippet on you

Real User Monitoring measures page load times in your visitors' own browsers. You paste one JavaScript snippet into your site. From there the snippet does the measuring, though it can sit on a live pa

A transaction monitor drives a real browser through an ordered list of steps you write: open a page, fill in a field, click something, check the result. One failing step fails the whole check. Use it

A transaction monitor replays a recorded browser journey on a schedule: log in, search, check out. It fails the run the moment one step cannot complete. Most of the failures that turn out to be false

An SSL monitor reads the live TLS certificate served by one hostname, records what it finds, and alerts you when the certificate is close to expiring or is no longer trusted. Registration and WHOIS fa

A domain monitor reads the registry's WHOIS record for one domain name, stores what it finds, and alerts you before the registration lapses. SSL Monitoring covers certificates. DNS Monitoring covers l

A DNS monitor queries the nameservers that are authoritative for one zone, directly, with no recursive cache in between. Every 5 minutes it asks those servers for the records you chose, compares the a

A DNS monitor records what your authoritative nameservers answer on its first sweep, then compares every later sweep against that recording. When an answer stops matching, Uptimia opens a change episo

A blacklist monitor sweeps your domain and every IP that sends or serves for it against 17 spam blacklists. A new listing opens an incident. Beyond the target you type in, it watches the web IP from y

A listing is one blacklist zone answering "yes" about one address you watch. Uptimia records each listing as its own episode and keeps sweeping while it stands, and the episode closes only once the zo

A virus monitor asks Google Web Risk about one URL on a schedule, and it opens an incident when Google flags that URL for malware, social engineering or unwanted software. Web Risk is what browsers us

A location profile is a saved set of monitoring probes with a name and a color, applied to as many monitors as you like. Seven profiles are built in: six cover the seven geographic regions, with Middl

Every monitor carries one free-text note, up to 500 characters of context for whoever picks up the alert at 03:00. Uptimia prints that note on the incident page, in every down and recovery alert email

"Our mail stopped being delivered" is rarely one failure. The mail host can be down. A sending IP can be sitting on a spam blacklist, an MX or SPF record can have been changed under you, or a record c

Uptimia's probes check from the public internet. A target they cannot open a connection to cannot be watched with an uptime monitor. That rules out an internal app, a staging box behind a VPN, a night

Uptime and availability are the same number under two labels: the share of the time you selected that a monitor was working. That number is the headline figure on the dashboard, on Uptime, Transaction