DBmarlin 6.7 with Sensor Status report, disk alerts and more AI models

A new Sensor Status report, control over which statistics you collect, disk alerting, the latest AI models from every provider, and a batch of usability fixes across the UI.

DBmarlin 6.7 is out now. We added a new screen which lets you know that your monitoring itself is healthy. For instance statistics you can now deciding exactly what gets collected.Alerting now extends to individual filesystems within a host. Alongside those, AI Co-pilot gains the latest generation of models and allows you to set your own custom models. Here's what's new.

Sensor Status report

The most significant addition in 6.7 is the new Sensor Status Report, which shows the status of your sensors over time.

Monitoring tools have a habit of failing quietly. A sensor stops collecting, and nobody notices until someone goes looking for data during an incident and finds a gap. The Sensor Status report makes that visible: rather than only telling you how a sensor is doing right now, it plots status historically so you can see when a sensor stopped, how long it was down, and whether a particular instance has a recurring problem.

If you're running DBmarlin across a large estate, this is the screen to check to see if any sensors are having connectivity issues.

New Statistics Settings screen

DBmarlin 6.7 adds a Statistics Settings screen that controls which instance statistics are collected.

Not every environment needs every statistic. Collecting everything on hundreds of instances costs storage and adds overhead. DBmarlin has a sensible default set of instance statistics but the new settings screen lets you add more when needed.

Disk alerts

Alert rules gain a new Disk Statistic category.

Disks filling can be very bad for database systems. With disk statistics now available as an alert category, you can set thresholds on the storage layer directly and be told before it becomes a problem.

Since 6.5, alert rules support separate Info, Warning and Critical thresholds, so a single disk rule can nudge you early and escalate properly when it matters.

More AI models in Co-pilot

AI Co-pilot has been updated with the latest models from all providers, including Fable 5 from Anthropic and Sol 5.6 from OpenAI.

Just as usefully, model names are now editable. Previously you were limited to whatever was in the pick list, which meant waiting for a DBmarlin release whenever a provider shipped something new. Now you can type in a model name directly - so if your organisation has access to a model that isn't listed yet, or you're pointing at a private deployment, you can use it straight away.

Windows upgrades keep your settings

Upgrading DBmarlin on Windows now preserves your SSL and SSO settings, along with the username running the DBmarlin Tomcat Service.

Anyone who has reconfigured SSO after an upgrade will appreciate this one. It removes a manual step that was easy to forget and awkward to diagnose when it went wrong.

Usability improvements

A number of smaller changes across the UI add up to a product that remembers what you were doing:

• Instance settings now have checkboxes for multi-selecting instances and hosts to start or stop, rather than working through them one at a time.
• Database Statistics retains your filters when you change the time range.
• SQL Statistics charts now save your chart selection.
• The top chart selection on the Activity screen is remembered between visits.
• Formatting changes to the alert rule list make it easier to scan.

Individually these are minor but together they remove a lot of the small re-work that adds.

Getting 6.7

DBmarlin 6.7 was released on 6th August 2026 and is available now. Existing customers can upgrade through the standard update process. Check the documentation for upgrade notes specific to your deployment type.

👉 Upgrade today to get the latest features and improvements.

Check out the release notes for a full list of changes.