Operations

Overview is the first screen for reviewing the current WebSpace runtime at a glance. Its summary shows cumulative requests, deployed databases, active APIs, and errors.

Runtime summary

Do not judge brief latency from the average alone. Review endpoint metrics under API · traffic together with the error log.

Databases

Review each DB's table and endpoint counts, requests, storage, last request, and runtime status. Expand a row to see DB, WAL, and SHM files, pool usage, and an endpoint permission summary.

Operators can stop or restart a DB. Stopping it can block new requests, including new WebSocket connections, so check active services and deployment work first.

API · traffic

Review request and error counts, average latency, and last request by database and endpoint. Narrow the problem using search and the DB, action, and status filters.

Before removing an endpoint with an old last-request time, check its usage cycle and retention purpose, then stop or clean it up as appropriate.

Error log

Review the time, HTTP status, DB, target, action, and processing time of recent failed requests. Distinguish authentication and permission errors from server errors, then investigate recurring databases or endpoints first.

A user's error message may differ by language. To narrow the cause, collect the time, request path, HTTP status, and response code or errorCode. User-facing messages do not include physical server paths or raw SQL. An authorized operator can inspect server logs for detailed diagnostics.