What we tested
This is an isolated test-environment exercise, not a customer incident or a production latency benchmark. A local HTTP server returned controlled JSON responses. The harness uses the actual response-check functions from the repository, with fetch routed to that local server only inside the harness. No remote requests, accounts, notification delivery or AI inference are involved.
Observed results
| Test state | HTTP response | Status check | Keyword “ready” | JSON database = up |
|---|---|---|---|---|
| Healthy | 200 | Pass | Pass | Pass |
| DB failed | 200 | Pass | Fail | Fail |
| HTTP 503 | 503 | Fail | Fail | Fail |
| Recovery | 200 | Pass | Pass | Pass |
The initial response was status: ready with dependencies.database: up. We then changed those values to degraded and down while keeping HTTP 200. The status-only monitor passed; both assertions failed. On HTTP 503 all three failed. Returning to the original response made all three pass.
Run a local response-assertion lab
Download the standalone teaching example and review it before running. It requires Node.js 20 or later and no additional packages:
curl -fsS https://statance.com/assets/marketing/examples/http-response-lab.mjs -o http-response-lab.mjs
# Review the downloaded file before running it.
node http-response-lab.mjsThis public example starts a loopback-only server, runs twelve assertions and closes the server. It demonstrates the same four response states but is not a distribution of Statance’s production probe code. The separate internal test that produced the results above used the repository probe functions with external networking disabled.
Read the standalone script and see its recorded assertion results. Neither test installs an agent or changes your services.
Download the captured JSON results. The file includes the run timestamp and a SHA-256 digest of the tested probe source. Observed response times are local measurements and must not be presented as multi-region detection or alert-delivery speed.
Experiment scope
The experiment demonstrates the configured response assertions and their recovery behavior. It does not exercise the production scheduler, regional consensus, incident state, email delivery, server-agent collection or AI investigation. A complete monitoring rehearsal should check those stages separately on a non-production endpoint.
Configure assertions for your application and understand the timing between checks.