Montray
github.com/dimonomid/montray- Category
- Developer Tools
- Rank
- No. 1382Tools index
Previous survey · No. 1347 ·
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Deployment & Operations
- GitHub
- 90 stars
- Latest release
- v2.1.0
- Date
About
Montray is a lightweight tray-icon monitoring utility that shows desktop alerts for systemd services and any other health check you can run from the command line, on local and remote machines. The author built it after a Syncthing service failed unnoticed for weeks and data stopped syncing.
At a glance
Montray puts the status of systemd services and command-line health checks in a desktop tray icon. It is worth trying when you want to notice a failing service while at your desk.
Good fit
Linux users watching a few machines or background services with checks they can express as commands.
Consider something else when
Use an on-call monitoring system when someone must receive alerts even while the desktop client is offline.
Start here
Add a harmless check with a controllable exit status. Flip it to failure and back and check what the tray and desktop notifications show.
Cost and requirements
The source is available under a BSD-style license. A background server runs the checks and a desktop client shows incidents. The maintainer reports testing on Linux.
Limits to know
Checks execute commands on the monitored host. For remote monitoring, review how the read-only status endpoint is exposed and authenticated.
Sources checked 2026-11-05. Source-based assessment.
Read the source review
What it does
Two programs split the job. A small background service runs on each machine you care about, polls systemd units and any shell command you point it at, and publishes the current list of problems over a read-only WebSocket feed. A desktop app connects to one or more of those services, merges their problems into one list, and turns a single tray icon green, blinking yellow or blinking red. You can snooze a problem so the icon stops nagging until it comes back.
Why it's ranked here
A narrow tool that does its one job with care. The service is Go, the desktop client is Rust with the Slint toolkit, and both ship as DEB and RPM packages. Remote machines are reachable three documented ways: plain loopback, a managed SSH tunnel, or TLS with a bearer token whose hash is all the server stores. The concurrency code is commented line by line, notifications are copied before being handed off so a later update cannot change one mid-read, and the core has end-to-end tests that drive a real failing check through to resolution.
What's good
The SSH tunnel support is the standout. The desktop app launches ssh itself, waits for a ready marker in its output, restarts it five seconds after a failure, and keeps only the last 1KB of its output for the error message. A silent connection is dropped after three missed ten-second heartbeats, and reconnects back off by one second per attempt up to ten. The default config is useful out of the box: any failed systemd unit is a warning, and under 100 MiB free on the root partition is an error.
Tradeoffs
The README says it has only been tested on Linux. The desktop client should run on Windows and macOS, but on those systems the service can only run shell checks, since there is no systemd to watch. Alerts go to a tray icon and desktop notifications only: the service can also write to a log file, and the code marks email and chat alerts as not yet built. Custom tunnel commands must not spawn child processes, because the app cannot clean them up yet. Running the full test suite needs GTK libraries and Node.js for a legacy client.
How to use it well
Best for one person with a laptop and a handful of personal servers who wants to notice a dead backup, sync or certificate-renewal service without running a monitoring stack. Install the server package on each box, keep it on loopback, and reach it through the built-in SSH tunnel. List the specific services you care about and mark anything other than active as an error. It is not a metrics system, has no history or dashboards, and does not page anyone when the laptop is closed.
Technical notes+
backend/core/core.go fans each tracker notification out to all messengers in parallel and waits, preserving order without letting a slow messenger block a healthy one, and logs when delivery is blocked; it updates the items board before notifying so WebSocket subscribers cannot miss a change (backend/itemsboard/items_board.go). statestracker/item_states_tracker.go keeps OK and not-OK maps keyed by item and copies each item into the notification slice so asynchronous consumers never see later mutation. backend/core/config.go allows exactly one of systemd or exec per collector and fileLogger or webserver per messenger, with a TODO for other messengers. wsclient/wsclient.go caps a single server message at 1 MiB, uses a 30 second read timeout from three 10 second heartbeats, linear reconnect backoff capped at 10 seconds, TLS 1.2 minimum with an optional extra CA file, and rejects bearer tokens containing whitespace. wsclient/tunnel.go supervises the tunnel process with a 5 second restart delay, a split-safe readiness probe writer, and a 1024-byte tail of output, with a TODO noting child processes of a tunnel command are not reaped. cmd/montray-ui/Cargo.toml pins Slint and builds release binaries with size optimisation, LTO and stripped symbols; a packaged feature disables in-app setup. cmd/montray-ui/src/app.rs keeps the Slint event loop on the main thread and Tokio on its own thread. docs/security.md documents the three supported connection modes and says the server stores only a SHA-256 hash of the token. backend/core/core_external_test.go covers incident start and resolution through a real exec probe, ambiguous and duplicate config rejection, and double Close.
Observed
- Languages
- Go background service; Rust desktop client built with Slint
- Packaging
- Prebuilt DEB and RPM packages for x86_64; make targets for building from source
- Interfaces
- Read-only WebSocket API from the service; tray icon, desktop notifications and native window in the client
- Checks supported
- systemd unit state and arbitrary shell commands
- Remote access
- Loopback, managed SSH tunnel, custom tunnel command, or TLS with bearer token
- Platform support
- Tested on Linux only per README; client described as expected to work on Windows and macOS
- Tests
- Go tests for the core in core_external_test.go; two native window tests skipped by default and need a real X11 session
- Alert outputs
- WebSocket feed and file logger; other messengers marked TODO in config.go
Read from README.md, go.mod, cmd/montray-server/main.go, cmd/montray-server/run.go, backend/core/core.go, backend/core/config.go, backend/collectors/collector.go, backend/itemsboard/items_board.go, statestracker/item_states_tracker.go, wsclient/wsclient.go, wsclient/tunnel.go, cmd/montray-ui/Cargo.toml, cmd/montray-ui/src/app.rs, docs/security.md, backend/core/core_external_test.go.
Tags
Tech Stack
Media
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.