- Home
- Monitoring
Every kind of check, one dashboard
17 monitor types, from a plain HTTPS request to a nightly backup that must phone home.
What can be monitored
A website going dark is only one of the ways a client's online presence fails. A certificate lapses on a Sunday. A domain renewal goes to a credit card that was cancelled last spring. A DNS record is edited by someone who meant to touch the staging zone. A WooCommerce checkout keeps returning 200 while the cart is empty. A cron job that sends invoices stops running and nothing complains. Each of those needs a different kind of check, and this page is the map of what Tenium offers for them.
Every type below shares the same machinery. Checks run from two live regions (Amsterdam and London), a failure is re-checked from other regions before anyone is paged, and the alert reaches you through whichever channel your plan includes. What differs is the question being asked: does the page respond, does the text appear, how many days of certificate are left, did the job report in on time.
Plan limits decide how many monitors you can run and how often they fire. Free gives 30 monitors every 5 min, with HTTP, keyword, ping and port checks. Starter at $7 a month raises that to 100 monitors every 1 min and unlocks JSON/API, DNS, UDP, cron heartbeat, SSL, domain and change checks. Pro at $29 runs 300 monitors every 30 s, and Agency at $59 allows 1000. Details on the pricing page.
How to choose
If you are setting up a new client site, start with a website check and a certificate check, add a domain check so the registration cannot lapse silently, and give WordPress or WooCommerce sites their dedicated templates. If you run servers or services, add port and ping checks for the things that are not web pages, and a heartbeat for each scheduled job. The sections below group the types by the question they answer, and each card links to a full page with the options, the failure modes and the plan it needs.
Is the site answering?
The checks most people start with: a URL, a status code and a body.
Website monitoring
HTTP(S) checks as often as every 30 s on Pro. Status code, response time, redirects and TLS expiry, with a failure re-checked from other regions before an alert goes out.
API monitoring
Call a REST endpoint on a schedule with the method, body and credentials it needs, then assert on the status code and a value inside the JSON response.
Keyword monitoring
Require a phrase to be on the page, or require another phrase to be absent. It is the cheapest way to notice a database error that your server answers with a happy status code.
Response time monitoring
Every check stores how long the response took. On Pro and Agency a slow threshold opens a degraded incident when the average of the last three checks is above it, so you hear about the creeping problem first.
WordPress monitoring
A keyword check on the home page, a status check on wp-login.php, a heartbeat for scheduled jobs, SSL expiry and DNS. Assemble them once per site from the standard monitor types.
WooCommerce monitoring
Watch a product page, the cart, the checkout and your payment webhook endpoint with keyword and status checks, so a broken button is caught before the first missed order.
Will it keep answering?
Quiet clocks that run out: certificates, registrations and records.
SSL monitoring
Look at the certificate your server really presents: expiry date, trust chain and hostname match, with warnings before it lapses and a failure the moment it is invalid.
Domain expiry monitoring
Tenium reads the registration expiry date from the registry over RDAP and warns you 30, 14 and 3 days before the domain runs out.
DNS monitoring
Resolve A, AAAA, CNAME, MX, NS or TXT records through public resolvers and compare the answer with the values you expect.
Web change detection
Tenium fetches a page, reduces it to visible text, hashes it and raises an alert when the hash changes. Point it at a price list, a terms page, a competitor or your own home page.
SLA monitoring
Uptime for each monitor is computed from confirmed incidents, with planned maintenance left out. It lands on a status page and in a monthly report, so the number you quote to a client is one you can show.
Third-party monitoring
Follow the status feeds of services your site depends on. When one turns non-operational you get a single alert, and incidents on the monitors you linked are tagged with that provider for the next 30 minutes.
Is the plumbing alive?
Lower-level reachability and the jobs that should report in.
Ping monitoring
One ICMP echo per check, with the round-trip time recorded. For hosts that do not speak HTTP, and a TCP fallback when ICMP is not possible.
Port monitoring
Open a TCP connection to any public host and port. If the handshake completes, the service is listening; if it is refused or times out from the confirming regions, you hear about it.
TCP monitoring
Open a TCP connection to a host and port on a schedule and record how long the handshake takes. It is the same check as port monitoring, described for people who search for it as TCP.
UDP port monitoring
Tenium sends a probe datagram to your host and port and expects any reply. It speaks real DNS on port 53 and real NTP on port 123, and works for other services that answer anything at all.
Cron job monitoring
Every heartbeat monitor has a ping URL. The job calls it when it finishes, and if the next ping does not arrive within the period plus grace, an incident opens.
Where to go next
If you manage many sites for clients, read how agencies use Tenium and the client workspaces feature. If you are comparing tools, the comparison pages set out prices side by side, and the free tools let you test a certificate, a DNS record or a response time without an account. Alerts, status pages and reports are described on the features overview.
Start monitoring in two minutes
30 monitors free, forever. No credit card. Moving from UptimeRobot? Import your monitors in one click with a read-only API key.