Atlas Knowledge Base
Dashboard
Desktop Tray Companion

Desktop Tray Companion


Monitoring Status at an overview

The desktop tray companion is a small app that sits in the Windows system tray or the macOS menu bar and shows the estate's single worst state at a glance. Its icon reflects the most serious condition anywhere in the estate, with a compact count beside it - how many sensors are Down and how many are at Warning - so you can tell whether anything needs you without opening a browser. One app covers both Windows and macOS.

What it lists

Open it and it drops down a list of every sensor that is not currently OK, most-serious-first, each with the message it is reporting right now. For a capacity sensor it shows the real amount next to the percentage - free space in gigabytes alongside the percent free - so "nearly full" is a number you can act on. Everything it shows comes straight from the same live state the dashboard reads.

Notifications on new problems

When a sensor newly goes Down, the companion raises a native notification - the standard Windows or macOS pop-up - once for that change. It also tells you once if it loses contact with the core. It is deliberately quiet: it notifies on the transition, so a lingering problem does not nag.

Read-only, with dashboard click-through

The companion only reads. It holds nothing beyond its own read login and can change nothing about the estate. When you want to act on what it shows, click any row (or "Open dashboard") and it opens the full dashboard in your browser, already the place where you can do something about it. It follows the same sign-in address that always reaches the active core.

Where to get it

The companion is downloaded from SBN Monitor's own install page. The builds for each platform are published there with a fingerprint for each, so you can confirm a download arrived intact, alongside a short configuration snippet and per-system install notes.

How it stays current

The companion keeps itself current. At startup, and once a day after that, it checks the published version list; if a newer build is available it raises a notification with a click-through to the download. Updating is a visible, one-click step - the companion verifies a new build is ours before installing it, and never accepts a build older than the one already running.



Was this helpful?