Managing monitors#

The Monitors page lists every monitor available to your organisation — the ones you’ve enrolled yourself, plus the shared fleet if you’re using it.

Adding more monitors#

Each additional monitor needs its own enrollment token. On the Add a monitor page, give the token a label (e.g. “home NAS”) so you can tell which agent it belongs to, and create it. One token per machine means you can revoke a single agent’s ability to (re-)enroll without touching anyone else’s.

Enable / disable#

Each of your own monitors has an Enable/Disable toggle. Disabling one stops it from authenticating with the server at all — it’s a real kill switch, not just a “paused” label — without losing its history or check assignments. Use it for a monitor you’re taking offline temporarily (a reboot, a network change) without wanting to lose its identity.

Resetting enrollment#

Reset enrollment invalidates a monitor’s current API key. The agent process will stop being able to sync until you run it again with a fresh enrollment token. Use -id <the monitor's id> (shown on this page) when you re-run it, so it re-adopts this same monitor — its history, check assignments and name — instead of enrolling as a brand-new one.

This is what you want after losing the machine’s local database, or if you suspect its API key has leaked.

Deleting a monitor#

Delete permanently removes a monitor and its check assignments. It’s only available once the monitor is already disabled — a safeguard against deleting something that’s still actively reporting. There’s no undo.

The shared monitor fleet#

Alongside monitors you run yourself, your organisation may have access to a shared monitor fleet — machines the platform operates on your behalf, useful for a quick multi-region view without standing up your own agents everywhere. See Shared vs. private monitors, and restricted checks for what sets it apart from your own monitors and which checks it’s eligible to run.

A shared monitor:

• Shows up in the Grid and By class dashboard views as its own class, separate from your own monitors.
• Is enabled or disabled by the platform, not by you — if one goes offline it’s out of your hands, but also not something you need to maintain.

Organisation settings has a toggle, Automatically include new shared monitors on non-restricted checks: on, every eligible check picks up new shared monitors automatically as they come online; off, you assign them to a check explicitly and nothing changes underneath you later. Turning the toggle off only stops future auto-attach — checks already assigned keep running where they are. A check can also opt out individually the moment you deliberately trim its monitor list, regardless of the organisation-wide setting.