Bug Fixes
- #9 — QNAP CPU, RAM, storage and disk details are now collected through the QTS API. CPU usage is read from QTS system metrics, RAM usage is calculated from total and free memory, installed disks are collected from SMART inventory, and volume usage is loaded with a File Station fallback.
- QNAP XML, CDATA and JSON response variants are supported, including existing SID authentication and username/password sessions.
- Missing permissions or unexpected API payloads no longer appear as valid zero values. OmniSight marks the integration as partial and displays a clear diagnostic instead.
Configuration Note
- The QNAP monitoring account must belong to the administrators group to access CPU, RAM, storage and disk metrics. QTS may allow a non-admin account to sign in while withholding these details.
Security and Quality
- Added regression coverage for QTS 5.2-style responses, four-NVMe TBS-464 inventory, JSON responses, permission failures and incomplete HTTP 200 responses.
- Updated the nested js-yaml dependency used by the Kubernetes client to 4.3.1; production dependency auditing is clean at the high-severity threshold.