Skip to content

ChoonDevelopRequest log

demoThis build is a demo. The catalog and detections are a fixed sample.Scopereading…
Never scannedcoverage unknown
Sound is used for one thing: a short tone when a long scan finishes while this tab is in the background. The A/B listening check plays audio either way, because there the sound is the evidence.

Request log

What was called, what came back, and how long did it take?

Server-side log

Reading the service request log…

Looked, the field is absent

Nothing in the service writes this log, so it is empty by construction rather than by quiet.

store.log_request exists (monitor/store.py:758) and is called from two tests and no request path — there is no logging middleware in service/api.py. The endpoint reports “no API request has been logged for this scope”, which is true and reads as “nobody called the API”. Those are different facts, and the second one cannot be established by this table until something writes to it.

This browser session

0calls made from the playground in this tab0 of 0returned an error status or never completed
Looked, found nothing

Nothing has been called from this browser session.

This log exists and holds no rows — an empty log rather than a missing one, and rather than a failure to read one. Making a call on the playground puts a row here immediately.

Held in sessionStorage: this tab, until it closes. A call made with curl, from another tab, or by anyone else is not here — and, because the server-side log is unwritten, is not recorded anywhere else either.