Go beyond basic checks with API response validation, database health monitoring and specialist monitor types for UK infrastructure.
When you need more than HTTP/Ping • JSON Query monitor • Database monitors • Other advanced monitor types • When to use advanced monitoring • FAQ
For most websites and services, HTTP or Ping is sufficient. But some situations call for deeper inspection. Your API might return 200 while the response body contains {"status":"error"}. You might need to confirm that a database behind your online shop accepts connections and responds to queries. That’s where advanced monitor types come in.
Good to know: most users only need HTTP, TCP and Ping. Advanced monitors are for specific technical needs — API validation, database health checks, IoT brokers, game servers. For standard websites, you can skip these.
Sends an HTTP request, parses the JSON body using JSONata expressions, and checks whether a specific field matches an expected value. If matches, up; if not, down.
JSONata is a lightweight query language. For most cases, a simple field name is enough.
https://api.example.com/healthstatus — top-level field from {"status":"ok"}data.health — nested from {"data":{"health":"green"}}$count(items) — array length$sum(prices) — numeric sumstatus expect ok.status, expected okquantity, expected > 0version, expected 2.5.0 — confirms release deployedTip: for auth-required APIs, use Headers: {"Authorization": "Bearer your-token"}. Change method to POST with a body if the health endpoint requires it.
Connect directly to databases, execute a query, verify the result. Confirms the database backing your UK website or application is actively responding, not just running.
mysql://user:password@hostname:3306/databasepostgres://user:password@hostname:5432/databasemssql://user:password@hostname:1433/databasemongodb://user:password@hostname:27017/databaseredis://user:password@hostname:6379 (or rediss:// for TLS)SELECT 1 is simplest (verifies connectivity + response). For richer checks: SELECT COUNT(*) FROM orders WHERE date = CURDATE()SELECT 1 confirms database up and accepting connectionsSELECT COUNT(*) FROM products with expected > 0Security note: create a dedicated read-only database user for monitoring. Never use application’s primary credentials. A user with SELECT-only privileges on limited tables is sufficient.
Unlimited monitors of every type
SmartXHosting Uptime Kuma Hosting — HTTP, JSON Query, database, gRPC, MQTT and all others. Single dashboard, daily backups, £1/month.
View Uptime Kuma HostingQ: What is JSON Query monitor?
A: HTTP request + JSONata expression to extract and compare a specific field from JSON response. Ideal for API health endpoints returning structured data.
Q: Can Uptime Kuma monitor a database?
A: Yes — MySQL, MariaDB, PostgreSQL, MS SQL, MongoDB, Redis. Connection string + test query like SELECT 1.
Q: What is JSONata?
A: Lightweight query language for JSON. In Uptime Kuma, extract values from API responses — e.g. status extracts top-level status field.
Q: Do I need advanced monitors?
A: Most users don’t. HTTP, TCP, Ping cover standard website and service checks. Advanced monitors are for specific API/database validation needs.
Q: What other advanced types are there?
A: gRPC, MQTT, Gamedig (game servers), Real Browser (Chromium-rendered pages for SPAs), Radius (authentication).