Uplance Monitor types JSON
Monitor an API by what it returns
Uplance reads the JSON your API returns and checks the fields inside it. A 200 with the wrong body is still a broken API.
Free for 10 monitors · no credit card
The problem
Your health endpoint returns 200 and the word ok while the queue behind it is forty minutes deep, or the dependency it reports on has been unreachable since the last deploy.
Any monitor can tell you the status code. Almost none can tell you that the number in the body is wrong.
What the check looks at
Fields in the body
Point at a field in the JSON and say what it has to be, so the check fails when the answer is wrong rather than only when it is missing.
Your own headers
Send the authentication and headers a real client sends; secrets are encrypted at rest and kept out of history.
Status and timing
Status code and response time, with anomaly detection that learns what's normal for this hour of the week.
Evidence when it breaks
DNS, TLS, connect and first-byte timings are captured with the failure, so the incident starts with evidence rather than a guess.
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 can I assert on?
- A field's value inside the returned JSON, the status code, and how long the response took. The intended use is your own health endpoint: return the numbers that matter and assert on them.
- Can it log in first?
- For a token in a header, yes — add it to the monitor. For anything that needs several steps, use a multi-step monitor, which chains requests and carries values between them.
- How do I monitor a whole user journey, not one endpoint?
- That is a browser monitor: a real Chromium session that clicks through the flow and fails on the step that broke.
- Can I check an API that is only reachable internally?
- Run a remote agent inside your network. It performs the check there and reports only the result out, so nothing has to be exposed to the internet.
Also monitored
Know it's down before your customers do.
10 monitors, 30 days of history, no credit card