Install the in-world monitor
Copy inworld/SimPulse-Monitor.lsl into a prim you own, rez it in the region to monitor, and generate a one-time activation code from the dashboard.
Available telemetry
The script reads only values available to LSL: region name, region FPS, time dilation, agent count, simulator hostname, simulator channel/version, region corner, object/owner identifiers and free script memory. API latency is measured by the monitor.
Detection semantics
Offline means the service missed the configured number of heartbeats. Recovery means telemetry resumed. Possible restart is inferred from a heartbeat gap plus a simulator-version change; it is never presented as a directly observed restart event.
Security
Activation codes are one-time and short lived. Successful activation returns a unique, revocable credential for that monitor. Heartbeats use HTTPS with the credential in an authorization header. The finished script contains no shared global secret.
Run locally
Without DATABASE_URL, the UI and read endpoints operate in demo mode. Use npm run demo:send to exercise ingestion against a running local service.