Hi, rgcda. The attribute packages from vC Ops 5 merged as a part of the policy in vR Ops 6. To illustrate a general procedure, in vR Ops 6 you would go through these steps to set different ...
See more...
Hi, rgcda. The attribute packages from vC Ops 5 merged as a part of the policy in vR Ops 6. To illustrate a general procedure, in vR Ops 6 you would go through these steps to set different threshold values to different groups of machines: 1. From 'Content > Symptom Definitions' menu, define symptoms using metrics for monitoring disk usage. (e.g. guestfilesystem|percentage) You can set thresholds like 85% = WARNING, 90% = IMMEDIATE, 95% = CRITICAL as a baseline for all machines. 2. From 'Content > Alert Definitions' menu, define an alert using symptoms you defined above. 3. From Environment menu, create a group that has the development machines in it. 4. From 'Administration > Policies' menu, create a new policy based on your default policy and override symptom threshold value (like 99% = CRITICAL) and assign the policy to the group you created. 5. From 'Content > Notifications' menu, define a notification rule if you need to receive an e-mail or something on the alert you defined. * Unlike Memory usage metrics (for example), a machine can have many disk drives that results to many instances of a same metric. (such as disk space usage for C:, D:, E:) So when you define a symptom using these metrics, you should set an 'instanced' property for it. (KB 2108273 : http://kb.vmware.com/kb/2108273) Regards, Ho-Sung.