Daniel

Hi first of all - APM is such a great tool - thx so much for it! I had an issue upgrading to the newest version 4.3 on my DS918+ with DSM 7.2.2 Update 3. The install wizard suggests to deselect 'Run after installation' on the next wizard page () - however, there was no such checkbox on that page () and therefore the automatic run after installation failed () leaving the package in a "damaged" state (). The "Repair" option just downloaded the package again and started the installation from scratch....

Hi first of all - APM is such a great tool - thx so much for it! I had an issue upgrading to the newest version 4.3 on my DS918+ with DSM 7.2.2 Update 3. The install wizard suggests to deselect 'Run after installation' on the next wizard page () - however, there was no such checkbox on that page () and therefore the automatic run after installation failed () leaving the package in a "damaged" state (). The "Repair" option just downloaded the package again and started the installation from scratch....

Hi first of all - APM is such a great tool - thx so much for it! I had an issue upgrading to the newest version 4.3 on my DS918+ with DSM 7.2.2 Update 3. The install wizard suggests to deselect 'Run after installation' on the next wizard page () - however, there was no such checkbox on that page () and therefore the automatic run after installation failed () leaving the package in a "damaged" state (). The "Repair" option just downloaded the package again and started the installation from scratch....

Hi, thanks for your answer. Implementing this functionality using uptime seems to be a good idea because this tool already provides the average CPU usage for certain time ranges (1, 5, 15 minutes), thus eliminating the risk of measuring spikes. I could imagine the frontend options as follows: Enabled: [ ] Interval to measure CPU usage in minutes: {Dropdown 1 | 5 | 15 } CPU threshold in %: <input field> On my NAS (DS918+ / DS1515+) I'd probably set the interval to 15 minutes and the threshold to ...

another example of a task with CPU load but almost no disk load is 'data cleaning' of a storage pool:

another example of a task of CPU load but almost no disk load is 'data cleaning' of a storage pool:

Add a CPU utilization check

Sure, it's the user's sole decision to update. But the update process itself should be automated, as millions of programs already do: 1. Download the update 2. Terminate the running KeePass instance 3. Install new version 4. Start KeePass