Salix Monitor 360 • Product update
Salix Monitor 360 update: companion apps, agent updates and launch polish
Written by Graeme Moignard
Published:
Last updated:
The last few days have been very companion-app heavy. Salix Monitor 360 now has a more useful Android app, a stronger iPhone and iPad test build, more practical agent-update groundwork and another round of small launch-quality fixes across alerts, monitors and admin views.
This is the kind of work that turns a product from “it can do the thing” into “it feels calmer when someone actually has to use it”. Less noise, clearer wording, better mobile behaviour and more obvious next steps when an alert lands.
Android has moved from useful build to real phone behaviour
The Android companion app has had one of the biggest practical jumps. Notifications are no longer just a checkbox on a development list. The app has been tested on a real Android phone with permission prompts, test notifications plus a real critical alert arriving from Salix Monitor 360.
The Android app also had a proper user-interface tidy. Notification settings are easier to understand, About information has been moved into the right place, the overview cards are clearer, alert history is more visible and notification tap-through now opens the relevant alert detail instead of leaving the user to go hunting for it.
Alert detail now explains more of the story
A monitoring app should not merely shout. It should explain. The companion app alert detail work has moved in that direction by showing clearer “what happened” information, latest response text and last-error detail where that data is available.
That matters on small screens. If someone is looking at an alert on a phone, they need a quick answer to “what broke?” and “what did the system last see?” without opening the full web app unless they need deeper investigation.
Alert flow
From warning to useful context
- Monitor health is checked in the background.
- Important failures become clear alert incidents.
- Companion apps show a push or desktop notification.
- Alert detail gives the user more context before they act.
- Notes, acknowledgement and snoozing stay focused on safe day-to-day response.
The iPhone and iPad app is now a proper test candidate
The iOS app has also moved forward quickly. The current test build runs in the iPhone simulator with the main working areas in place: sign-in, overview, alerts, alert detail, team notes, snoozing, monitors, agents plus About.
Notification groundwork has started as well. The app can request notification permission, receive an Apple push token and register that device with Salix Monitor 360. The next job is final push sending, which depends on the Apple developer-side setup being available, but the app-side and server-side registration path is now in much better shape.
Core screens
Working test flow
The main app areas now run cleanly enough for proper product testing.
Notification setup
Device registration
The iOS app can register a push-capable device with Salix Monitor 360.
Visual tidy
Calmer mobile UI
Cards, detail screens and wording are being shaped for small-screen everyday use.
Agents are being prepared for easier updates
Installed agents are the quiet workers in a monitoring product, so update handling matters. Recent work has added the foundation for clearer agent version checks and safer future agent updates across Linux, macOS and Windows.
The macOS agent has had particular attention, including install-help polish, network-context reporting and a self-update-capable test path. The point is simple: a monitoring system should not leave admins guessing which machines are current and which need attention.
Admin views and access wording are getting sharper
There has also been more polish around organisation scope, monitor views and read-only admin visibility. In plain English: people should see the right things for their role and the app should be clear about what they are allowed to do.
That includes clearer companion-app access summaries, safer read-only overview behaviour for higher-level monitoring views and continued work on monitor and alert wording. It is not glamorous, but it is the difference between a tool that feels trustworthy and one that makes the user wonder if it is showing too much, too little or the wrong thing entirely.
The pattern is launch readiness, not feature confetti
A lot of this recent work is not about dropping a giant new menu item into the product. It is about making the product steadier: better phone alerts, clearer incident detail, more useful agents, safer role visibility, cleaner wording plus fewer rough edges in the daily workflow.
That is the direction for Salix Monitor 360 as it heads towards launch: practical monitoring, calmer alerts, companion apps that are useful away from the desk and enough polish that the product feels like it belongs in day-to-day business use rather than hiding in a development cave with a mug of cold coffee.