Repository navigation
2026.11.04.11
This is the first stable release of the Data Volume Monitor continuation maintained by alexphillips-dev. It brings the development branch to the Stable (main) channel, with vnStat 2.14, the updated Data Volume Monitor artwork, clearer threshold settings, and the reliability fixes described below.
Data Volume Monitor tracks network interface usage in Unraid and can send notifications, stop/start selected Docker containers, disconnect/reconnect VM network links, or run custom functions when configured limits change state. Traffic remains interface based; container and VM matching supplies labels rather than independent application accounting.
Highlights
- Updated backend: bundled
vnstat,vnstatd, andvnstatiupgraded from 2.12 to 2.14, built from verified upstream source with recorded build inputs and binary hashes. - Consistent threshold tables: eight primary rules and six secondary slots expose thresholds, units, and Docker/VM actions clearly. Primary settings now use the same table style as Secondary, with horizontal scrolling on narrow screens.
- Clear threshold status: Disabled is red, Enabled is green, and invalid input is red. These labels describe the entered limit; notification and action switches remain separate.
- More reliable monitoring: polling avoids overlapping requests, reports stale or unavailable data, and preserves the last successful measurements when a refresh fails.
- Safer configuration and recovery: editor boundaries, save races, backup verification, custom storage paths, service errors, and concurrent notification checks have regression coverage.
- Deliberate action testing: Service Check is diagnostic only. Test Configured Actions requires confirmation, and recorded failures can be retried after current configuration and threshold checks.
- Stable and Development channels: installed version/channel information is visible in settings. Each channel keeps its own installer, package, and future-update URLs.
Installation and upgrade
For a new Stable installation, open Plugins → Install Plugin in Unraid and enter:
https://raw.githubusercontent.com/alexphillips-dev/Data-Volume-Monitor/main/plugin/dvm.plg
The manifest declares Unraid 6.8.3 or newer, and the packages target x86_64. The backend requires compatible host SQLite and GD libraries; it does not replace those host libraries. The declared minimum is not a claim of live testing on every Unraid version.
If you already use this continuation's Development channel, moving to Stable is an in-place channel switch. Follow the channel-switch instructions, including the destination-version check. Do not uninstall to switch channels: uninstall deletes plugin settings, backups, and traffic history. Development installations continue checking dev until deliberately switched.
If you use the original dwdvm plugin, follow Migration from the original plugin first. Stop the old service, copy configuration/scripts and the newest stopped database outside the old plugin's directories, and verify those independent backups before removal. The original and continued plugins must not be installed together. This release does not automatically migrate the old plugin identity.
After updating, refresh the settings page and check DVM Version / Channel and DVM Backend. Review saved interface selections, thresholds, and action switches before running configured actions.
Validation and host acceptance
The release is qualified with the repository's Linux validation entry point: Python regressions, PHP and JavaScript fixtures, syntax/ShellCheck checks, tracked-file checks, backend source/signature and binary checks, channel checks, exact package contents and permissions, and deterministic package rebuilding. The Python suite contains 142 tests; PHP and JavaScript fixtures run separately in the same validator.
Backend fixtures exercise all three executables, all six PNG output modes, the report formats, structured threshold boundaries, custom paths, and preservation of a database created by vnStat 2.12. Primary-table fixtures cover all eight rows and 48 fields through simulated Apply/reload. Browser simulations cover desktop and phone widths with light and dark fixture styles.
Automated fixtures do not establish live Unraid installation, native theme integration, real Docker/libvirt actions, or reboot persistence. Those observations remain separate in the Host acceptance checklist. Back up important history before migration or channel changes.
Documentation and support
- README and operating guide
- User and maintainer wiki
- Bug reports, feature requests, support, and documentation issues
Include plugin/channel, Unraid, and backend versions when reporting a problem. Remove credentials, server names, public IP addresses, and other private information from screenshots and logs.
Complete changes from the original version to this release
This cumulative list covers the continuation's work through 2026.11.04.11, rather than only the final development increment. The original baseline has manifest version 2026.10.16, plugin archive 2025.08.21, and backend vnstat-2.12-x86_64-1_slack14.2. Earlier upstream fixes remain documented in the manifest changelog.
Maintenance, identity, and artwork
- Continued maintenance under
alexphillips-dev/Data-Volume-Monitor, retaining required license/copyright notices. - Changed the active plugin identity and paths from
dwdvmtodvm, including settings routes, configuration locations, scripts, downloads, updates, and support links. - Added installer conflict checks for the original plugin and Network Stats, which share vnStat service/database ownership.
- Replaced active plugin artwork with the supplied Data Volume Monitor image and applied it to both the Plugins listing and Settings tile.
- Removed the obsolete contributing file and kept local agent/tool configuration untracked.
- Added ignore rules for environments, caches, credentials, runtime databases, logs, temporary/recovery files, and diagnostic exports while retaining required packages and checksums.
- Preserved executable script modes for package installation and service execution.
Initial audit fixes
- Restricted configuration-editor access to supported files, checking path boundaries, traversal, symlinks, and file types.
- Distinguished unavailable/error threshold results from exceeded limits so failed queries do not trigger threshold actions or appear as confirmed healthy data.
- Fenced stale editor responses and save identity so switching files cannot save one file's content into another.
- Handled partial/failed paired saves, preserved previous contents and modes on handled failures, and supported intentional empty saves.
- Propagated service, wrapper, installer, reset, and package-removal failures before dependent operations proceed.
- Serialized concurrent notification checks with a real lock and covered overlap and lock-acquisition failure.
- Checked VM lookup, interface discovery, and network-link command results before reporting success.
- Evaluated all six custom thresholds and aggregated matching rules instead of losing later rules for the same interface/direction/period.
- Corrected combined interface/service filtering, exclusions, and PHP-to-JavaScript encoding.
- Preserved Docker/VM names, including spaces, during virtual-interface matching and checked peer/bridge matching boundaries.
- Corrected the custom-alarm 45-minute schedule across hour boundaries.
- Honored effective custom database and PID paths in service checks, persistence, restoration, editor guards, and resets; retained the selected storage location during resets.
- Preserved existing build deliverables when manifest validation, source reads, or handled publication steps fail, with rollback/recovery coverage.
Monitoring, reports, and display
- Prevented overlapping polling requests and added finite request timeouts.
- Retained the last complete measurements after failed or partial refreshes, with visible stale/unavailable status and recovery behavior.
- Prevented late responses from updating pages after navigation and resumed polling after back/forward cache restoration.
- Separated valid traffic measurements from threshold-only query errors and covered missing interface/service data.
- Escaped interface/service names and report text, retained complete filtered labels, and used safe generated image names and image URL handling.
- Added content-based cache invalidation for shipped UI scripts.
- Kept the traffic overview visible while grouping detailed reports in a labeled section that starts collapsed.
- Added spacing between footer inbound/outbound usage and colored the direction arrows.
- Kept primary and secondary threshold/action controls readable and editable when limits are disabled.
- Added live red Disabled, green Enabled, and red Invalid labels, including whole-number and unsigned 64-bit boundary validation.
- Converted Primary Interface Thresholds and User Actions into eight table rows, preserving all 48 field identities, saved values, unit choices, and workload selections.
- Added accessible labels and a keyboard-focusable horizontal scroll region to the primary table.
Configuration, persistence, and action outcomes
- Preserved saved interfaces and Docker/VM targets when discovery is empty or fails, identifying unavailable selections instead of silently replacing them.
- Distinguished successful empty inventory from command failure and preserved special characters in option labels/values.
- Added actionable editor error messages and unsaved-change protection for file switching, Cancel, navigation, and edits made during saves.
- Verified shutdown-hook installation/removal across supported host layouts and reported persistence setup failures.
- Bound database backups to their source path and checksum, retained a previous verified generation, and staged restoration before creating the runtime database.
- Rejected corrupt, incomplete, wrong-path, or mismatched backups and prevented invalid current data from replacing a valid retained generation.
- Made Service Check diagnostic only, without running real workload/custom actions or changing transition markers/outcome records.
- Added a separately confirmed Test Configured Actions control and a validated custom-alarm example.
- Recorded per-rule action attempts and component results, including interrupted or unconfirmed completion.
- Added deliberate retries for recorded failed components, guarded by current rule/configuration/script/state checks; stale results do not automatically retry actions.
Backend upgrade and compatibility
- Upgraded bundled
vnstat,vnstatd, andvnstatifrom 2.12 to 2.14. - Added a pinned, reproducible dependency build from signed upstream source, with recorded build inputs, provenance metadata, executable hashes, and required license/documentation files.
- Verified baseline x86_64 architecture, runtime loader/libraries, and glibc compatibility limits without replacing host libraries.
- Documented the newer vnStat configuration options while retaining DVM defaults and saved configuration.
- Compared native threshold behavior across periods, directions, unit modes, and boundary values; checked invalid input, overflow, missing data, and custom effective paths.
- Exercised a vnStat 2.12 database with 2.14 and verified retained traffic, schema, and alias data while vnStat version metadata updates.
- Exercised all three backend executables, six PNG modes, JSON/XML escaping, and PHP text/image/dual report paths in isolated fixtures.
Release channels, validation, documentation, and GitHub support
- Added explicit Stable (
main) and Development (dev) installer/download/update URLs and packaged release metadata; settings show the installed version/channel without guessing from Git state. - Added guarded release preparation, calendar/version ordering checks, concurrent-edit detection, transactional generated-file publication, and Git mode preservation.
- Added exact source/package inventory, permissions, checksums, provenance, deterministic rebuild, ignored-file, and channel validation.
- Added Python, PHP, JavaScript, native-backend, and browser-fixture coverage for the audited changes; automated tests use isolated files, databases, and mocked workload commands.
- Reserved hosted GitHub Actions validation for
mainpushes and pull requests targetingmain; development publication uses explicit local validation and--no-verifycommits/pushes. - Rewrote the README and expanded the wiki across setup, channels, migration, thresholds, notifications, actions, reports, editing, storage/recovery, removal, troubleshooting, backend builds, development, and host acceptance.
- Added bug-report, feature-request, support/configuration-help, and documentation issue forms with matching category labels,
needs-triage, privacy reminders, and a wiki link. - Published this first stable release with a version-only title and retained the complete cumulative change list here.