-
[NOTE] When upgrading to 0.3.0+, supporters will need to log in again. Thank you for your continued support.
With this release comes support for remote logging and the Unmanic Central service. Unmanic Central is a self-hosted management and monitoring platform that lets you collect, store, and visualise logs and metrics from all your Unmanic installations in one place.Key components:
- Unmanic Central Datastore
A resilient, self-hosted store for Unmanic logs, metrics and data. - Unmanic Central Frontend
A new web interface where you can build custom dashboards, configure real-time views, and drill down into every event and metric across your fleet.
What you can do with Unmanic Central:
- Centralise log collection
Route logs (with automatic retry and buffering) from each Unmanic instance into one unified store. - Monitor performance
Track library scan duration, service CPU/memory usage, plugin progress, file-processing changes (size, duration), and more—all correlated by installation. - Visualise and alert
Create and share dashboards in the Central frontend to focus on metrics and events that matter, and integrate with Grafana for advanced querying and visualisation. - Extend with Grafana
Optionally connect Grafana directly to your Central Datastore to build custom dashboards, set alerts, and leverage the full power of your data.
Availability:
Unmanic Central is a supporter-only feature. - Unmanic Central Datastore
Service
- [NEW] Add initial log‐forwarding feature with on-disk buffering and remote endpoint support
- Create remote‐log buffer with retention of 2 weeks to survive endpoint outages
- Include installation name as a label in all remote logs
- [NEW] Introduce METRIC logs for library scan duration
- [NEW] Emit overall service resource-usage metrics (CPU, memory) as METRIC logs
- [NEW] Emit per-worker progress metrics (CPU%, memory%, elapsed time, progress%) as METRIC logs
- [NEW] Support a new “DATA” log type and send structured data to Unmanic Central
- [NEW] Add DATA logs for library scan metrics
- [FIX] Resolve supporter session & login issues introduced by recent API changes
- [FIX] Ensure logs generated before remote-logging is enabled are still captured and forwarded
Plugin executor
- [NEW] Add “event runners” to emit lifecycle events at key task execution points
- [NEW] Introduce a shared, task-scoped data store for plugins via
TaskDataStore
- [NEW] Enable spawning plugin work in isolated subprocesses with the new
PluginChildProcess
helper (live logs & progress) - [IMPR] Enhance child-process cleanup with a global PID registry and guaranteed termination (including paused processes)
- [FIX] Ensure all plugin-spawned subprocesses are reliably terminated on service shutdown
Docker
- [FIX] Correct the Docker development-environment run script
Front-end
- [IMPR] Force immediate registration-status refresh after obtaining a new app token
- [FIX] Restore supporter-login flow following recent API changes
- [FIX] Allow sign-out when the remote API is unreachable