w.Monitor Public
Read-only monitoring
Loading monitoring space…

Service status

Waiting for service status

One-command device setup

Choose initial settings and run once on the device. Adjust them online after connecting.

Agent settings
Installation notes and credentials

First setup creates an anonymous space and status page, then prints recovery and page links. The first device’s name, status and basic metrics will be public.

Linux AMD64 / ARM64. Requires curl, Bash and SHA-256 tools. The Agent runs in the foreground and updates remain manual.

Recover a monitoring space

Enter your saved private recovery key to recover the same space and devices.

Save your new recovery key

Shown only once. Save it to recover this space in another browser.

After saving, sign in with W-ID to claim this space and recover it in other browsers. Signing out does not unlink the account.

Connect a device

Choose initial settings and run once on the device. Adjust them online after connecting.

Agent settings
Installation notes and credentials

The command contains a private registration key. Generating a new key replaces the old key without affecting registered devices.

Linux AMD64 / ARM64. Requires curl, Bash and SHA-256 tools. The Agent runs in the foreground and updates remain manual.

Agent settings

Online settings

Only the collection settings above can change. The Agent receives them on its next report, or when it reconnects.

New status page

Select devices to publish
Public columns

Name, online state and last report are always public. Select basic metrics separately; network and history are off by default. History includes selected metrics only. Full collection remains private.

Public pages hide device identifiers, IP addresses, logs and full reports.

UPTIME

Device availability uses heartbeats. Your selected Agent probes services locally. An offline probe makes service status unknown.

State changes

My service checks

Fixed HTTP GET or TCP connection checks only. No redirects, response bodies, scripts, commands, custom headers or credentials.

Device details

Default egress counts default-route interfaces and may include LAN traffic on those interfaces. Internal classes are interface observations, not deduplicated LAN bandwidth. Network history includes only confirmed egress measurements.

Historical trends

Overview metrics refresh live. Details below come from the last full report; expand collectors to see every field.

Raw snapshot (JSON)