Upgrade action required: Omnibus users
v1.67.0 upgrades the embedded InfluxDB runtime from 2.2 to 2.9.1. Existing Omnibus installations must back up their InfluxDB data before the first 2.9.1 startup.
- Stop the Scrutiny container.
- Back up the complete host directory mounted at
/opt/scrutiny/influxdb. For the example Compose deployment, this is./influxdb. For the Unraid template, the default is/mnt/user/appdata/scrutiny/influxdb. - Set
SCRUTINY_INFLUXDB_29_BACKUP_CONFIRMED=true. - Start Scrutiny and confirm the application and InfluxDB health checks are healthy.
The updated Omnibus image blocks InfluxDB startup when existing data is detected without this acknowledgement. Fresh installations start normally and do not require confirmation. After a confirmed upgrade, a persistent marker prevents repeated prompts.
If an earlier latest image already started InfluxDB 2.9.1, stop Scrutiny and back up the current InfluxDB directory before making further changes.
See the Omnibus InfluxDB 2.9 upgrade instructions and rollback guidance.
Highlights
InfluxDB 2.9.1
- Upgrades the embedded Omnibus database from InfluxDB 2.2 to 2.9.1.
- Keeps token hashing disabled for rollback compatibility.
- Documents downgrade and token-recovery procedures.
- Adds a pre-start backup-confirmation gate for existing Omnibus data.
Collector omnibus image
- Adds
ghcr.io/starosdev/scrutiny:latest-collector-omnibusfor hub-and-spoke deployments. - Bundles SMART, ZFS, MDADM, Btrfs, filesystem, and performance collectors in one spoke image.
- Includes Docker Compose, Unraid, documentation, and image-build support.
MDADM reliability
- Persists
host_idduring array re-registration so RAID arrays group correctly by host. - Handles MDADM discovery variants and missing device lists without crashing the RAID Arrays page.
- Existing arrays need one fresh MDADM collection to backfill
host_idbefore host headings appear.
Logging
- Honors configured startup log levels across Scrutiny containers.
- Allows the startup banner to be suppressed.
- Improves structured service-startup logging.
Fixed issues
- #636: Suppress the ASCII startup logo and honor log settings.
- #640: Group MDADM arrays by host.
- #642: Provide a combined collector omnibus image.
- #652: Prevent null MDADM device lists from crashing the RAID Arrays page.