Skip to content

Monitoring Overview

Monitoring 9 min read
On this page

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 #

The control panel groups the twelve into three sets, and the order below matches your sidebar. Click Monitoring to expand the list. The Monitoring row carries your fleet total, and each type you already use shows its own count.

The Uptimia sidebar with Monitoring expanded, listing every monitor family under Availability, Experience and Domain & Trust, including Security, with a count beside each family and a red or amber count of the ones with a problem.Enlarge
FamilyGroupWhat one monitor watches
UptimeAvailabilityOne endpoint over HTTP, HTTPS, TCP, Ping, DNS, UDP, SMTP, POP3 or IMAP
TransactionAvailabilityA recorded multi-step browser journey, replayed on a schedule
APIAvailabilityAn ordered chain of HTTP requests with assertions and variables
HeartbeatAvailabilityAn inbound ping your job sends: Uptimia alerts when it stops
ServerAvailabilityCPU, memory, disk, network and load, reported by an agent on your host
SpeedExperienceFull page load timing and Core Web Vitals for one URL
Real UserExperienceLoad timings collected from your actual visitors' browsers
SSLDomain & TrustCertificate validity, chain and expiry for one host
DomainDomain & TrustRegistration expiry, registrar and nameservers from WHOIS
DNSDomain & TrustOne zone at its authoritative nameservers, plus record changes
SecurityDomain & TrustMalware and phishing verdicts for one URL, plus checks of its headers, TLS, software versions and email setup
BlacklistDomain & TrustYour domain and sending IPs across 17 spam blacklists

Note: Server is the one type that can be missing from your sidebar. It renders only for accounts whose plan grants server monitoring, so an absent Server row means your plan does not include it. Every other type shows for every account.

Availability Checks #

Uptime #

Use this when you want to know whether a site or service is reachable. An uptime monitor checks one endpoint from the probe locations you pick and opens an incident when the checks fail.

The What should we check? control in the editor splits into three sub-tabs:

Sub-tabWhat it covers
WebHTTP and HTTPS
EmailSMTP, POP3 and IMAP mail-server connections
NetworkTCP port, Ping (ICMP), DNS resolution and UDP

All three sub-tabs create uptime monitors, drawn from the same uptime pool. Uptime is the right first monitor for most websites. Read Uptime Monitoring.

Transaction #

Use this when one request cannot prove the thing works: a login, a checkout, a search that has to return results. A transaction monitor replays a scripted journey in a real browser, using an 18-action catalog grouped as Navigate, Interact and Verify, and the check fails when a step cannot complete or an assertion does not hold. Read Transaction Monitoring.

API #

Use this when you need to exercise an API the way a client does. One API monitor runs an ordered chain of 1 to 15 HTTP requests, each with its own method, headers, body and assertions, and you can pull a value out of one response and reuse it in the next request as {{variables}}. Read API Monitoring.

Heartbeat #

Use this for work that runs on your side: a cron job, a queue worker, a nightly backup, a device in the field. There is no URL for Uptimia to call. This is the one family where the ping travels inbound. Your job calls the unique ping URL Uptimia gives it, and Uptimia opens an incident when the expected ping does not arrive within the grace period. A monitor can expect a ping on a fixed interval or on a 5-field cron expression. On top of the ping itself, a job can send a Start or a Fail signal, so a hang or a self-reported failure is caught too. A heartbeat monitor arms itself on its first real ping, so it cannot alert before you have wired it up. Read Heartbeat Monitoring.

Server #

Use this when you want the numbers from inside the machine rather than from outside it. A lightweight agent runs on your host and posts CPU, memory, disk, network and load, on a report interval fixed to one of four values: 30 or 60 seconds, 2 minutes or 5 minutes, defaulting to 30 seconds. Alert rules fire on thresholds you set, and silence lasting more than three report intervals opens an offline incident. The incident opens on the next sweep. Read Server Monitoring, and Installing the Uptimia Server Agent for the install.

Experience Checks #

Speed #

Use this when you care how long a page takes to finish loading. A speed monitor loads the whole page in headless Chrome from your selected locations. It records the total load time, a breakdown by resource content-type, and an own-domain versus third-party split. The same run yields lab Core Web Vitals (LCP, FCP, TTFB and CLS), and you can set per-metric vitals budgets and dead-element alerts, both of which raise Degraded rather than Down. INP is absent because it needs a real visitor interacting with the page. Read Speed Monitoring.

Real User #

Use this when you want the numbers from your visitors' own browsers rather than a lab measurement. You add a JavaScript snippet to your pages, and it feeds Real User Monitoring. There are no checks and no check frequency; data arrives as people browse. Uptimia counts pageviews per month instead of checks. Because there are no checks, Real User is the one family with no rows on the Logs page, and the one family left out of the account's fleet availability average. Read Real User Monitoring (RUM).

Domain & Trust Checks #

SSL #

Use this to stop a certificate expiring without anyone noticing. An SSL monitor tracks validity, the chain and the expiry date for one host, and warns you a chosen number of days ahead. Read SSL Monitoring.

Domain #

Use this to protect the registration itself. A domain monitor reads WHOIS for one domain and reports registration status, expiry date, registrar and nameservers, refreshed on a cadence you set. Read Domain Monitoring.

DNS #

Use this to watch the zone itself. A DNS monitor queries your zone at its authoritative nameservers rather than at a cache. Each sweep reports two things:

  • Per-nameserver health: reachability over UDP and TCP, answer time, whether the server says the answer is authoritative, SOA serial agreement across servers, and whether a server answers recursive queries it should refuse.
  • Record changes, measured against a baseline you keep.

Sweeps run every 5 minutes and the cadence is not adjustable. Read DNS Monitoring.

Security #

Use this to find out when browsers start warning people away from your site, and to catch common security problems on the site behind a URL. At the monitor's check interval Uptimia runs a Google Web Risk lookup for malware, social engineering and unwanted software. This lookup cannot be switched off. Once a day the monitor also runs check groups you can switch on or off: software versions, security headers, TLS settings, email authentication (SPF and DMARC), page content, DNS records (CAA and DNSSEC), mail encryption (STARTTLS) and MTA-STS. Each problem is listed as a finding with a severity. A finding at the level you alert on opens an incident, and the monitor then reads Warning rather than Down, so the time does not count as downtime. On Professional and up, verifying that you own the domain unlocks extra checks. A Security monitor has no locations to pick, so there are no per-location results to read. Read Security Monitoring.

Blacklist #

Use this when your mail has to arrive. A blacklist monitor sweeps 17 DNSBL spam blacklists in three impact tiers. Each sweep covers:

  • your domain
  • the IP behind its A record
  • the IP behind its lowest-priority MX record
  • up to five dedicated sending IPs you add

This is a different thing from security monitoring: browsers flag a site, and mail servers reject a sender. A Security monitor checks your SPF, DMARC and MTA-STS records, but only a blacklist monitor tells you a mail server's blocklist has listed you. Read Blacklist Monitoring.

Every Family Draws on Its Own Plan Pool #

Mixing types is normal. An uptime monitor, an SSL monitor and a speed monitor on one site is a common setup, but each family is counted against its own per-plan allowance, so "mix and match" has a ceiling. On Free the only non-zero pools are 1 uptime monitor and 1 API monitor; every other family is 0 on that plan. Speed and Transaction share a single Advanced checks pool rather than one each, so you split that allowance between them however you like. The full per-plan table is in Plan Limits and Quotas.

Settings That Apply Across Monitor Types #

TopicWhat it does
Outage confirmationHow many confirming checks a failure needs before an incident opens: 1 to 3, default 3. It lives on the editor's Advanced tab, under Outage confirmation. Offered on seven families: Uptime, SSL, Speed, Domain, Transaction, API and DNS
Monitoring locationsWhich probes run your checks, and the 6-probe floor on a custom selection
Location profilesA saved probe set reused across monitors, editable in one place
Monitor groupsGrouping monitors for filtering, reports and team scoping
Monitor templatesSaved editor settings applied to new monitors
Monitor notesA short runbook note that travels to the incident page, the alert email and the webhook
Escalation policiesA tiered ladder that pages one group, waits, then pages the next
Alert groupingCollapsing a storm of related incidents into one digest
Manual incidentsOpening an incident yourself with Open manual incident in a monitor's actions menu, for a problem the checks cannot see. Offered on every family except Real User. While it is open, Uptimia stops opening or closing incidents on that monitor automatically until you resolve it
Maintenance windowsSuppressing checks and alerts during planned work
Monitor statusesWhat Up, Down, Degraded, Warning, Awaiting data, Paused, Maintenance and Suspended mean on a monitor row

Allowlisting the probe addresses in a firewall, WAF or CDN applies to every family Uptimia checks from the outside. See Whitelisting Uptimia's Probe IPs.

Was this helpful?

Your answer helps the team improve this article.

Still need help?

Uptimia Bot answers right away and passes you to the team when it can't.

Source: https://help.uptimia.com/help/a/monitoring-overview