Release v0.118.0
Sep 27, 2026
Legacy alerting retires and network checks move to Monitors, backups and restores get sturdier, memory module inventory arrives, and security hardening lands across the server, agent and Breeze Helper. Upgrade recommended.
Alerting & Monitoring
- Legacy alerting is retired. Every alert now runs through Monitors. On first start the server converts any legacy alert sources that are left and lists anything it couldn't convert in a banner under Alerts → Monitors, so you can recreate those by hand.
- Network checks are now monitors. Create and edit them under Alerts → Monitors with an asset picker. The Network page keeps Assets, SNMP Templates and a read-only Results view, and you can convert an existing check into a monitor from there with its history and open alerts kept.
- Maintenance windows suppress monitor alerts again. On v0.117.0, Suppress alerts didn't stop alerts from monitors.
- Bandwidth, disk I/O, network-error and patch-compliance monitors now evaluate in the units they display. Bandwidth thresholds were being compared about 8× too high, so a threshold that never fired before may fire now.
- Hardware health is now a regular filter field that works in saved filters and dynamic groups.
Backup & Recovery
- A backup that produced a snapshot but couldn't read some files now shows as 'Completed with errors' in amber instead of a green Completed, and backup continuity monitors can alert on it.
- Stalled backup jobs are now detected and cleaned up, and uploads of a single large file show progress as they go.
- Bare-metal rebuilds stop when they stop making progress instead of at a fixed 4-hour limit, and Hyper-V backups check for free space before they start.
- Hyper-V restore, restore as VM and instant boot report failures clearly instead of reporting success. Needs the 0.118 agent.
- Snapshots stored under a destination prefix can be recovered and deleted again, files whose names differ only by capitalization are kept separately, and system-state backups keep partial registry data and name what failed.
Devices, Patching & Software
- Memory module inventory: the device Hardware tab shows every memory slot, filled or empty, with total slots, maximum capacity and soldered memory. Needs the 0.118 agent.
- Breeze now spots agents stuck retrying the same self-update and flags them with an 'Update stuck' badge. No agent change needed.
- Devices with Breeze Assist turned on but not installed are called out on the device page and in the device list.
- Failed patch installs now show as failed, with the reason, instead of 'Pending approval'.
- The CVE view can group by software: one outdated application is one row, and Remediate queues one install per device.
- Software Library installs accept extra vendor success exit codes per version, and Remediate on the compliance dashboard previews exactly which devices and uninstalls it will queue before you confirm.
Security & Platform
- Security hardening across the server, the agent and Breeze Helper. Upgrade recommended. Several of these fixes take effect on a device only once its agent and Breeze Helper are on 0.118.
- Password changes, password resets and MFA resets now end that user's live remote sessions and invalidate the API keys they created before the change, and more sensitive actions ask for a fresh MFA check.
- New usage limits on public downloads, password-reset emails and agent traffic keep one noisy source from affecting everyone else.
- PAM elevation-audit export: download elevation events with their full request context as CSV or JSONL, one organization at a time.
- Remote sessions wait for the end user to answer a consent prompt and show why a consent was refused.
This release finishes the move from legacy alerting to Monitors. The old alert rules and service and process monitoring are retired, and network checks are now monitors you create under Alerts → Monitors. The server converts anything that’s left on first start and lists what it couldn’t convert, so you know what to recreate. Maintenance windows suppress monitor alerts again, and several monitor types now evaluate in the units they show. Expect a bandwidth threshold that never fired to start firing if it was set too low.
Backups and restores get a round of reliability work. A backup that missed files now says so instead of showing green. Stalled jobs get cleaned up. Bare-metal rebuilds stop when they stop making progress, and Hyper-V restores report real failures. On the device side you get memory module inventory, stuck-update detection, and failed patch installs that show their reason.
This release includes security hardening across the server, the agent and Breeze Helper. Upgrading is recommended. Several of the fixes only take effect on a device once its agent and Breeze Helper are on 0.118, so check that the agent rollout has finished across your fleet. Self-hosters, read before you upgrade: run Convert everything on v0.117.0 first and review any refusals, and take a database backup. Dynamic groups that match on device-reported fields such as hostname, tags or installed software no longer act as targets for scripts, automations and several policy features. DR plan steps that stored credentials need to be saved again without them. The GitHub release notes have the full upgrade detail.