When Veeam connects a VeeamPowerNFS, often this datastore latency is higher than our required numbers.
Well, you'd say, no problem, just add this to the alarm excludes for that datastore, and then use a nice grouping expressions to ignore those datastores starting with "Veeam".
No problem, I've done that, and I dont get the alarm anymore for the datastore. The problem is I get the alarm for Host. Because the actual error is:
"Datastore Write Latency" (xx ms) is above define threshold (yy ms) for "VeeamBackup_xxxxxx"
"The host disk (vmhba) has exceeded the threshold for total latency.
Shouldn't Veeam One correlate the two, and see that my datastore is something I have used as an excluded as well. (Even the the alarm object is for my host?)