It is recommending you delete memory and leave it with 4.62 GB rather than the 32 GB with which it is presently configured.
EDIT: I saw the bottom half of your screenshot. You're calculating memory based on both demand and consumed. Those are two very different calculation methods. For the demand calculation, you need to remove memory. For consume, you need to add memory. If this is some sort of database workload like Exchange, SQL, or others, the consumed calculation is very misleading as those applications will consume every bit of memory you give them. This doesn't mean it's actually using it.
Hi daphnissov,
I am still learning about this product and will be building a new vROPS infra with custom policies for our company soon. Unfortunately, I'm still unable to make head or toe of the Memory Consumed against the Memory Demand metrics and wasn't able to find anything that was able to explain it well to me, do you happen to have a good link that could help me (and the OP as well it seems) out?
Thank you.
Some resources that would really help both of you out are the following books. Although they are a little old, most of the concepts are still the same.
Mastering vRealize Operations Manager
VMware vRealize Operations Performance and Capacity Management
Take a look at vXpress there are some vert y good webinars on capacity
Just saw your reply to the vROPS rant, added vXpress to my bookmarks and will go through all of them. Thank you!