robotesting, VMTurbo calculates the Utilization Index (UI), aka the Price Index (because of the economic theory behind the analytics engine) on a logarithmic scale. For the StorageAmount commodity (how much data is actually written to your datastores), this is calculated by default out of 90% of your Datastore's total capacity (as a way of preventing the DS from completely filling up -- this allows us to automatically move VMs away from these datastores before this happens).

Since you're using the free version of our software, you should see Warnings/Recommendations in the lists describing (possibly 'critical') "Storage Amount congestion" because some of these datastores are exceeding the 90% value (>90% used out of a 90% effective capacity means the datastore is too full. However, you won't see actual To Do recommendations about what to do to address the issue. I'm not sure why UI is the only thing that's showing as Red for you, though. I might expect that StorageAmount should need to be red too.

And to answer your previous question, the Utilization Index is calculated depending on utilization of any of the "Commodities" -- i.e. the performance metrics like Storage Amount, Storage Provisioned, IOPS, and Latency -- that the Datastore "Sells" to the Virtual Machines that store files there.

Hi there, what are the values you have in this instance for IOPS, Latency and Storage? If you hover over the bars, you will get a value for each. The UI is calculated from the 3 other metrics as you said.

Yes, there is an Alert and for 5 Datastores it says: StorageLatency Congestion...but the Latency is Green with 3.34% that's why I don't understand...how can it be all ok where the Alert says StorageLatency Congestion.

Even though these UI are 100 still doesn't make sense because all others are low and on Green...so not quite sure how VMTurbo is deciding that UI is bad...; I'm not saying it should be good either but if I cannot identify why the UI is bad VMTurbo doesn't really help on this instance.

Do you have any Placement policies (VMTurbo Workload Segments or Storage DRS rules) in place? If, for example, you have a rule that says "Keep this group of VMs on different datastores" then the UI would shoot past 100 if you had multiple VMs from this group running in the same place (however you would also notice a To Do recommendation of the "Compliance" category telling you to move the offending VMs).

There are probably other things that could be causing it off-hand that I can't think of at the moment. Like thodoris77 up above, it's hard to guess what it could be without taking a look at it.

I think what I'm trying to understand is more how the UI is calculated? do IOPS, Latency, Write & Read are the only things taken into account? I think the answer is no, as it seems that there are more things as well...

The Storage SAN which I have is not quite new and I know that there are some performance issues, especially where there are NL-SAS disks but the info in VMTurbo Monitor is red herring for my case.

There are no Storage DRS rules and I only use the Free VMTurbo version to see how it can help me.

I understand it is more difficult to understand from a forum post, I try my best to explain what I have on my VMTurbo console.

Looking at your screenshot, the storage amount seems to be the metric pushing the UI to 100. The UI is made up of a number of metrics, including IOPS, Latency, storage amount (in use), storage provisioned (which is relevant if you use thin provisioning). Storage amount to me looks like it's close to 70%?

robotesting, VMTurbo calculates the Utilization Index (UI), aka the Price Index (because of the economic theory behind the analytics engine) on a logarithmic scale. For the StorageAmount commodity (how much data is actually written to your datastores), this is calculated by default out of 90% of your Datastore's total capacity (as a way of preventing the DS from completely filling up -- this allows us to automatically move VMs away from these datastores before this happens).

Since you're using the free version of our software, you should see Warnings/Recommendations in the lists describing (possibly 'critical') "Storage Amount congestion" because some of these datastores are exceeding the 90% value (>90% used out of a 90% effective capacity means the datastore is too full. However, you won't see actual To Do recommendations about what to do to address the issue. I'm not sure why UI is the only thing that's showing as Red for you, though. I might expect that StorageAmount should need to be red too.

And to answer your previous question, the Utilization Index is calculated depending on utilization of any of the "Commodities" -- i.e. the performance metrics like Storage Amount, Storage Provisioned, IOPS, and Latency -- that the Datastore "Sells" to the Virtual Machines that store files there.

The best guess is that because some of the Datastores are almost full ... 90% of capacity the UI index = RED + Alert

Yes, if UI is based on these commodities ( Storage, IOPS and latency) I would expect to see the Storage on red as well...but probably it's green because that would be for the TOTAL Storage on ALL Datastores.

I have some Datastores based on some SATA disks where there isn't too much data stored, I use those as shared SCRATCH drives and not for Live Production Servers.

So the answer would be that under Storage the UI alert is for those at almost maximum capacity but the Storage, IOPS & Latency is for the total Storage...a bit confusing though...