Hi Albert,
// EDITED: Didn't noticed at first that you already made changes. I couldn't see the images first. Did you made the changes on all objects? On a specific scope?
When this alarm was created (new in the latest version) it was tested and fine-tuned against many different setups and environments, but obviously, not against every possible environment that exists in the world
The thresholds are:
For VMware VMs
* Average CPU usage is above 70.0% and datastore write rate is 40 MB/s for 5 minutes. - gives a warning
* Average CPU usage is above 80.0% and datastore write rate is 60 MB/s for 5 minutes. - gives an error
For Hyper-V VMs
* Total run time is above 70% and virtual storage write is above 40 MB/s for 5 minutes. - gives a warning
* Total run time is above 80% and virtual storage write is above 60 MB/s for 5 minutes. - gives an error
Best thing you could do is modify the alarm to make it more suitable for your environment so it doesn't give you the false alarms anymore on those specific servers.
More information on modifying the alarms can be found here:
https://helpcenter.veeam.com/docs/one/a ... tml?ver=95
Also, don't forget you can work with scopes to fine-tune the alarm only for those objects:
https://helpcenter.veeam.com/docs/one/a ... tml?ver=95
Hope it helps
Mike