All,
I created an alert for Time Remaining for VM CPU and Memory the other day using the threshold of less than 100 days on the Time Remaining Symptoms. I was able to get CPU and Memory Events to fire and got them sent to our MoM for eventual ticketing. I then canceled the events in vROps and changed the threshold to less than 30 days. The next round of the alert firing I still had some alerts with the message text still refering to the old threshold of 100. I then removed the Alrert definitions, canceled the alerts to clear them and the re-created the Alert definition with new names however I get the same result.
The following are snipets from the alert on the vROps server:
The one still using the old threshold:
AffectedResourceAdapterInstanceResourceName ::
VMwareAdapter Instance:DEV vCenter
NSXAdapter Instance:itsusmpsdnsx01d
AlertOwner ::
Anomalies ::
VirtualMachine:ITSUSMPWSD01992 - [cpu|timeRemaining] - HT below 0 < 100
The one using the new threshold:
AffectedResourceAdapterInstanceResourceName ::
VMwareAdapter Instance:DEV vCenter
NSXAdapter Instance:itsusmpsdnsx01d
AlertOwner ::
Anomalies ::
VirtualMachine:ITSUSMPWSD02003 - [cpu|timeRemaining] - HT below 0 < 30
However both seem to be referencing the new threshold.
