Uplance Monitor types Keyword
Monitor what the page actually says
Uplance reads the response body and checks whether the text you named is there — or whether text that should never appear has shown up.
Free for 10 monitors · no credit card
The problem
The framework caught the exception, rendered an apology page, and returned 200 with it. Every status-code monitor on earth calls that healthy.
The same is true of a maintenance page, an empty product list, and a login form served where a dashboard should be.
What the check looks at
Text that must be there
Name a phrase only a working page contains, and the check fails when it is missing.
Text that must not
Or name one that only a broken page contains — an error string, a maintenance notice — and the check fails when it appears.
The status code too
The response code and timing are still recorded, so you see both of the reasons a page can be wrong.
What it saw
Failures keep enough of the response to show why they failed, rather than only saying the keyword was missing.
And the alert actually arrives
Most monitoring tools are fine until the one time the alert doesn't arrive. Uplance is built so that can't happen quietly.
- Every alert is written to an outbox before it is sent, and retried for about fifty minutes. A restart doesn't lose it.
- Once a week, a real test event is sent through every channel you've configured, and you're told which ones failed.
- If the alert pipeline is in trouble, the dashboard says so — it isn't buried in a log file.
- If the checker itself stops, the health endpoint returns 503 so an outside heartbeat can page you, and your status page says monitoring has stopped instead of showing stale green.
Common questions
- What should I match on?
- Something a working page always has and a broken one never does — a string from the footer, a heading, a total. Avoid anything that changes with the logged-in user or the time of day.
- Does it see content rendered by JavaScript?
- No: this checks the response body as it arrives, which is fast and cheap. For a page that builds itself in the browser, use a browser monitor.
- Can I use it to watch someone else's page for changes?
- Yes — a price, a status notice, a published version number. It is a plain HTTP request, so treat the other site's terms and rate limits as your responsibility.
- Is it case-sensitive?
- No. The comparison ignores case, so a heading that changes capitalisation doesn't page you at 3am.
Also monitored
Know it's down before your customers do.
10 monitors, 30 days of history, no credit card