I have a problem about Memory metric. I am using vROps 8.6 I have to get a report every week from AVG of memory usage for each VM (Most of my VM's OS are Linux ) As there are many metrics for memory in vROps I am so confuse which one should select in vROps 8.6
for example I don't know have to look in Guest metrics or Memory metrics
I'd say if you want to have the GuestOS average Memory Usage for a week, create a report that is scheduled each week that has a view in which the metric Memory | Guest Usage (KB) is averaged. You can choose the view for the metric to view it as averaged, max, min etc.
Hope this helpe.s
Thanks. But as you know when our OS is Linux most of our memory will be pick as cache and when the OS need will be use it for example when our system has about 32G , about 15G will be pick as cache and just 8G will be active and use by OS. Actually I think here memory usage for that OS is 8G . Also as you know better than me, memory metrics in that doc are not clear
Hi @BA ,
Not sure if I know better than you, just trying to help here. But If that is the case, you might want to have a look at the following metrics:
Mem|Guest Demand (KB)
Mem|Guest Active Memory (%)
Guest|Free Memory
Guest|Physical Usable Memory
Try and compare the results from these to check if they come close to your needs. If this doesn't work for you, you might have to create your own metric to get the results you need.
Is VMware tools installed on those servers?
Memory|Utilization (KB) is preferred as it uses guest OS memory.
If you want to bypass that, you can use Guest|Needed Memory (KB) for the guest OS point of view and Memory|Consumed (KB) for the host's point of view.
Check out below blog as well, despite it is from 2019 it's still valid.
@RickVerstegen . Yes VMware Tools has been installed on all of them but as memory usage in Linux has difference with the windows . While our OS is linux it will be pick up a lot of memory as cache and will be return to OS when it needs. So I am looking for a metric that does not calculate cache/buffer memory just calculate current memory usage
I would still say have a look at the mentioned metrics and try and work out what works best for your specific use case.