The Big Screen dashboard is becoming a clearer status wall

One of the biggest pieces of work this week has been the new Big Screen overview for Salix Monitor 360. The aim is simple: give organisation admins and super users a display-friendly page that can sit on a large monitor or TV and answer the important question without hunting through several admin pages: “what needs attention right now?”

That means the most useful totals and status panels need to be near the top, the layout needs to work from across a room and the data has to be trusted. A big screen full of pretty numbers is only useful if the numbers are being gathered consistently.

Behind that visible page, the supporting data work is being tidied so the dashboard, Big Screen view and related pages stay consistent. The public result should be simple: fewer confusing differences between screens and more trustworthy totals.

The monitor forms got a little less trusting

Real product work often comes from silly little discoveries. This week’s favourite was noticing that a monitor could be saved without filling out the form properly.

That is exactly the sort of issue that matters before a product reaches more users. You can build alert engines, dashboards, agents and reporting tools, but basic form handling still has to be solid. The fix is not glamorous, but it matters: better validation, clearer user guidance and fewer ways to create nonsense monitors by accident.

Dev life, captured in one commit message

Blank monitor forms are now handled properly

A small but very real quality fix: monitor creation and editing should guide people clearly and stop empty or malformed details before anything gets saved.

The bigger thread here is making monitor setup clearer for ordinary users. Where a field expects a full URL, it should say so. Where it expects a bare host or domain, it should say that too. Monitoring forms should not be cryptic little goblin contracts.

Agents and service monitoring kept getting tougher

The agent work has continued across Windows, Linux and macOS. The Windows guidance now explains the Scheduled Task setup more clearly, because a manual run is useful for testing but not enough for a live monitoring setup.

The Linux and macOS agent guidance has also been tightened. The help is clearer, the agent behaviour is more resilient and the app is more careful about the information agents provide.

Service monitoring has been another important thread. Windows and Linux service pickers have been improved, Linux service states are being handled more cleanly and service monitors are becoming more practical for checking whether the background bits that matter are actually running.

The network view became more readable

The network map has had more visual and behaviour polish too. Icons are cleaner, operating-system glyphs are more consistent, the inspect panel has been improved and monitor status colours are being made easier to understand at a glance.

Disabled monitors now deserve their own sensible treatment instead of being shoved into vague unknown states. That sounds small, but it is a good example of the product becoming less confusing. “Disabled” and “broken” are not the same thing and the interface should not blur them together.

Reports, branding and admin scope got more careful

A lot of work has gone into making reporting and branding behave properly across different organisation types.

Organisation reports should honour the right branding. Root organisation reports should use the root branding. Child organisation reports should inherit that branding unless self-branding is explicitly allowed. Super-admin and whole-app views should not accidentally wander out wearing a client logo. That would be the software equivalent of turning up to a meeting with someone else’s name badge.

The reporting scope rules matter just as much. Organisation admins should see the organisations they control, including linked child organisations where appropriate, but not unrelated organisations. Super users need broader views, but those views should still be labelled clearly.

Alongside that, admin pages have continued to get safer and clearer: global monitor visibility for super users, request telemetry options for system diagnostics and more careful separation between app-wide views and organisation-level views.

Companion apps kept moving

The companion-app side of Salix Monitor 360 has also kept moving forward. The Windows Alert Desk build has been through another round of clean-up, including fixing text display issues and restoring agent images. It is becoming a more professional daily-use Windows app rather than just a technical sidecar.

Android and iOS work have continued as separate companion-app streams, with each platform being prepared in a way that fits its own publishing and testing expectations.

The shape of the product is becoming clearer: the web app remains the control centre, while the companion apps become the everyday alert desk in your tray, pocket or hand. Same alert data, same permissions, quicker access.

The public website and downloads pages are catching up

The public-facing side is getting attention as well. Download pages, version notes, checksums, Android links, Windows unsigned-app guidance and screenshot planning have all been part of the week.

This matters because software does not only need to work. People need to understand what it is, how to install it, what warning messages to expect and which download source is trusted. Clear download pages save support time and reduce the “is this safe?” fog.

A practical week of progress

This has been one of those weeks where the work looks scattered from the outside: dashboards, monitors, agents, network maps, reports, apps, downloads, website copy and form validation. Underneath, though, it is all the same job.

Salix Monitor 360 is being shaped into something calmer, clearer and harder to misuse. The big features need the small fixes. The shiny dashboards need the boring collectors. The companion apps need careful permissions. The monitor forms need to stop blank nonsense at the door.

That is the product slowly becoming less of a pile of features and more of a dependable working tool.

Final thought

Hot weeks are not always bad weeks. Sometimes they are when the dashboard gets clearer, the forms get stricter, the agents get tougher, the apps get closer and one ridiculous little commit message earns its place in the blog.

Now the goal is to keep turning that practical work into a calmer, clearer product for real customers.