We watch it, patch it, and fix it before you file a ticket.
ClearWatch is the platform our engineers run your estate on: monitoring, patching and remote support in one place, with your servers, workstations, hypervisors and network hardware all in the same list. It is not a dashboard we bolt on at the end. It is how the work gets done.
One list, not one tool per kind of thing.
Most monitoring stops at the machines with an agent on them, which is where the interesting failures start. ClearWatch treats a hypervisor guest, a switch answering SNMP and a laptop in someone's kitchen as the same kind of thing: something with a state, a history, and somebody who needs to know when it changes.
Servers, desktops and laptops
One agent on Windows, Linux and macOS reporting processor, memory, disk and volume pressure, the services that are supposed to be running, and the state of the machine itself. Metrics are rolled up and kept, so a slow decline is visible as a trend rather than as a surprise.
Virtual infrastructure
Proxmox nodes and clusters, including datacenter, storage, Ceph and backup state, and VMware through vSphere with its own inventory and alarms. Guests are pulled in from the host that reports them, so a virtual machine does not have to be found by hand to be watched.
Switches, firewalls and UPS hardware
SNMP monitoring against a library of vendor MIBs, so a device is offered the readings it actually answered rather than everything its manufacturer's file claims. Anything without an agent is watched through ClearBridge: a nominated machine on the same network doing the checking.
The paths between sites
A traceroute from a chosen machine to an address you care about, run on a schedule and drawn hop by hop, so the answer to a bad morning is which hop and since when rather than a shrug about the internet.
Whatever else matters to you
Monitors are named sets of checks with their own Normal, Warning and Failed thresholds, attached to machines by link rather than by copy, so changing one changes it everywhere it is used. Templates decide which machines get which monitors as they arrive.
Everything, arranged by site
Devices belong to locations and sub-locations inside your organization, so a multi-site business sees one site at a time or all of them, and a patch window follows the timezone the machines are actually in.
Updates on a schedule you set, not whenever a machine feels like it.
Windows Update and Linux apt packages are approved, grouped and deployed on your own maintenance windows, with the result of every run recorded per machine. macOS is reported on, so you can see what is outstanding there while the deployment side is still being built.
Policies decide what gets approved and when it reboots. Groups decide which machines a policy applies to. A Proxmox host is never rebooted by a patch run, because the guests on it are somebody's working day.
The tools are in the same place as the alarm.
Remote control
Take the screen with the person's consent, including through a firewall that allows nothing inbound. Sessions can be recorded and played back afterwards.
Tools that do not need a session
Browse the registry, read the Event Viewer, open a terminal or run a saved script against a machine, without interrupting whoever is using it.
Alarms worth reading
A fault raises one alarm rather than a stream, and an alarm can be snoozed on a machine you already know about, so the next one still means something.
ClearWatch is switched on per client, by us.
There is no self-service sign-up, and creating an account does not give you ClearWatch. It comes with a managed agreement: we enable it for your organization, license the devices it covers, and give the people you nominate access to your own estate and nobody else's.
If you already have a ClearPath account and ClearWatch is not open to you, that is usually because it has not been enabled for your organization yet, or because your access covers other parts of the portal. Either way it is one conversation to sort out.