Salix Monitor 360 • Product update
Salix Monitor 360 August update: reliability, clearer security and the road to launch
Written by Graeme Moignard
Published:
Last updated:
Since the 10th August update, the work has shifted away from adding headline features and towards making the whole product calmer, clearer and more dependable. The next few weeks are about going through the entire Salix Monitor 360 codebase, which has become a fairly huge code monster by now, ironing out bugs and improving the interface before the product is let loose in the public domain.
That has already produced useful changes around monitor setup, vulnerability scanning, Network Topology, organisation navigation, Windows Agent onboarding and the companion apps. This update is deliberately about the parts users will notice, rather than the less glamorous plumbing behind them.
Monitoring polish
Safer scan results
Network Topology
Problem reporting
Windows setup
Companion apps
Four languages
September launch
Monitoring is getting easier to set up and trust
The API Endpoint Monitor now has a much simpler URL-first setup. For the common case, you can enter the endpoint you want to check and get on with it, while the less common options stay available without dominating the page.
- TLS/SSL certificate monitoring is back where it belongs in the New Monitor screen, with clearer expiry information and more useful renewal guidance when a certificate is getting close to its threshold.
- A broad end-to-end acceptance pass has exercised HTTP/HTTPS, DNS, SMTP, Page Content, Heartbeat/Cron, Linux monitoring, TCP/UDP, process, service, disk, CPU, memory, load, traceroute and TLS/SSL checks.
- HTTP/HTTPS and Page Content monitoring have also been checked independently so their different use cases remain clear and predictable.
Vulnerability scanning now tells you how much to trust the result
One of the more important changes is how Salix Monitor 360 treats scan quality. A scan can now be shown as successfully validated, completed with reduced coverage, or genuinely failed. That sounds small, but it stops a partial scan from looking more authoritative than it really is.
- A degraded scan can still show useful findings, but it cannot silently replace the latest trusted security posture or manufacture a reassuring overall grade from incomplete evidence.
- ZAP web application scanning now crawls more of the target before assessing it, which produces broader coverage and more meaningful findings and severities.
- Nuclei findings and remediation wording have also been tightened so useful evidence is retained and the advice better matches the issue that was actually found.
A lot of the current work is simply making the product nicer to use
This is the stage of the build where small pieces of friction matter. A monitor can be technically perfect and still be annoying if the surrounding screen is cluttered, confusing or awkward on a smaller display.
- Users can report a problem from inside Salix Monitor 360 and track its status without leaving the application.
- Network Topology now starts with a cleaner automatic layout, preserves saved layouts and has better filtering for newer monitor types, with clearer icons, legends and translated labels.
- Organisation switching is more compact and makes the active organisation easier to see, while long organisation names and smaller screens are handled more gracefully.
- A wider interface polish pass has removed more English fallbacks, improved responsive tables and made customer-facing icons more consistent.
Windows Agent setup is clearer in every supported language
The Windows Agent setup page has had a full localisation and onboarding pass. The instructions and screenshots now match British English, French, German and Spanish, including the PowerShell confirmation letter shown by the user’s localised Windows installation.
It is a small detail, but it matters. A translated guide should not tell somebody to press an English confirmation key when their own PowerShell prompt is asking for something different.
Companion apps are operational, but launch distribution will be pragmatic
The companion apps themselves are fully operational. Store and signing administration may not all be completed by the main SaaS launch, and that distinction is worth making clear now.
iPhone and iPad
Available on the App Store
The iOS companion app is already available through Apple’s App Store and will remain the straightforward installation route for iPhone and iPad users.
Android
Direct APK at launch
The Android app is expected to be provided as a downloadable APK initially rather than through Google Play. It will install normally once Android is allowed to install the downloaded app, but the Play Store process and its testing requirements are likely to come later.
Windows
Working app, signing still to finish
The Windows companion app will download and install, but Windows may show an unrecognised-app or security warning until the code-signing and reputation work is complete. That is a distribution and trust-presentation issue rather than a problem with the app itself.
A realistic note about French, German and Spanish
British English is the source language and remains the most directly verifiable version. French, German and Spanish have had a very large amount of localisation work, with natural language prioritised over literal word-for-word translation.
Even so, no claim is being made that every translated sentence will be 100% native-perfect when Salix Monitor 360 first goes live in September. Proper human review takes time, especially with technical terminology and sentences whose meaning depends on where they appear in the application.
There may still be the odd awkward phrase, wrong nuance or piece of wording that needs tidying once native speakers put real human eyes on it. The majority of early users are expected to be English-speaking, so the initial impact should be limited, but translation corrections will remain part of the launch-quality work rather than being treated as finished forever.
The road to September
The focus for the next few weeks is deliberately unglamorous: work through the big codebase, find the rough edges, fix them, and repeat. The public launch should feel stable and understandable rather than simply feature-rich.
NOW
Full product sweep
Work through screens, monitor flows, translations and responsive layouts to find bugs and awkward user journeys.
NEXT
Fix, simplify and retest
Tighten anything that is confusing, verify the important monitoring paths again and keep polishing the companion experience.
SEPTEMBER
Public SaaS launch
Open Salix Monitor 360 more widely once the quality pass is where it needs to be, with post-launch fixes continuing as real users exercise it.
Nearly there, but not rushing the last bit
Salix Monitor 360 already does a lot. The job now is not to keep bolting on features for the sake of it, but to make the large collection of monitoring, alerting, reporting, security and companion-app features feel like one coherent product.
September remains the target for the main SaaS launch. If something still feels rough, fixing it properly matters more than pretending a date on the calendar outweighs the experience people actually get.
Current focus
Bug fixing, UI polish, trustworthy monitoring results, language review and launch readiness.
You can see the current public overview on the Salix Monitor 360 page.