Skip to content

Monitoring Page

This page covers Monitoring in the hosted dashboard’s sidebar, part of the Hosted tier and above. It answers two questions an agent’s own machine can’t be trusted to answer: is Omnodex still watching there, and if something changed, did a person change it?

It’s built from two sources that check each other. Each connected machine sends the hosted service a small status report about every 15 minutes, which the agent can’t edit once it’s sent. And when someone installs, removes or pauses monitoring with the CLI, the machine records a marker in your encrypted data. The hosted service can read the reports but not the markers, so your browser does the matching after it decrypts them.

One row per machine that has reported, with its status, each agent platform and how it’s monitored, when the last report arrived and which CLI version it runs. A machine that’s paused shows Recording paused or Uploads paused under its status.

StatusWhat it means
ReportingA report arrived in the last hour
QuietNo report for an hour, and no agent session was open at the last one. This is normal: laptops sleep and machines get switched off
Not reporting (LOW)No report for an hour, and a session was open at the last one
Not reporting (HIGH)Quiet with a session open for more than 24 hours, while another machine on your account kept reporting

A machine that’s alone on its account never goes HIGH from time alone, because there’s nothing to compare it with. The hosted service looks for machines past 24 hours once an hour, so the change to HIGH can come up to an hour late.

Each platform reads as one of these:

Platform stateWhat the machine reported
monitoredHooks, plugin and proxy entry are in place
recording pausedRecording is paused on the machine
hooks missing, hooks switched offThe agent’s Omnodex hooks are gone, or present but turned off
plugin missing, plugin switched offThe Omnodex plugin is gone, or turned off
proxy entry missingThe MCP proxy entry is gone from the agent’s configuration

A platform the machine stops reporting at all counts as not installed, and isn’t listed.

A machine that stops reporting looks the same from the outside whether it went to sleep, lost its connection, crashed or had monitoring stopped. So the page never guesses. A silence says what was seen, and what happened when the machine came back:

  • Back, monitoring as it was. Nothing changed while it was gone.
  • Back, with less monitoring than before. Something was removed or switched off while it was quiet.
  • Back, reporting a change no marker explains. The machine found a change to its own monitoring that nobody recorded with the CLI. This makes the silence HIGH.
  • Still quiet. The page lists the possibilities and leaves it there.

Every change to monitoring across your machines, newest first, for the last 120 days. Use the machine menu above it to see one machine. It includes:

  • Hooks, plugins and proxy entries installed or removed, with whether it was done from a terminal or without a person at one. A removal without a person at a terminal is MEDIUM.
  • Projects left out of monitoring or brought back, and every-project monitoring turned on or off.
  • CLI updates, connecting and disconnecting, enforcement mode changes, watched paths added or removed, and the local event log being cleared.
  • Pauses to recording, uploads or enforcement, and when each one ended.
  • Silences and how they ended.
  • A platform’s state going down, for example from monitored to hooks missing.

That last one is where the two sources meet. If a change recorded on the machine explains it, the line says so. If nothing does, it’s HIGH: the machine reported less monitoring and nobody recorded a reason.

Only the status reports: platform states, pause flags, whether a session is open, the CLI version and a count of unexplained changes. No paths, commands or activity. The markers that explain a change, and the machine names on this page, are decrypted in your browser. What Omnodex Can See lists every field.