---
title: "Datastores View"
slug: "datastores-view"
updated: 2025-07-02T15:34:41Z
published: 2025-07-02T15:34:41Z
canonical: "support.controlup.com/datastores-view"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.controlup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Datastores View

## How to Exclude a Datastore from the View

There may be datastores under your hypervisor for which you don't need monitoring and which may add unnecessary data to your view.

To exclude any datastores from monitoring:

 1. In the organization tree, right-click the hypervisor whose datastores you want to exclude from this view's data and select **Properties.**
 2. In the **Excluded Datastores**	  field, specify the datastores that you want excluded from monitoring. Separate multiple values with a comma. You can also use an asterisk * as a wildcard value.
:::(Info) (Note)
 This field appears only for those hypervisors that have datastores.
:::
 3. Reconnect to the hypervisor for the changes to take effect.



## Column Descriptions for Datastores View

<table>
  <tbody>
    <tr>
      <td>
        <p>
          <strong>% Free Space</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">The percentage of free space available on the datastore</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Capacity</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">The capacity of the datastore in gigabytes</span>
        </p>
      </td>
    </tr>
    <tr>
        <td>
            <p> <strong>Capacity Deduplication</strong></p>
        </td>
        <td>
        <p>
          <span style="font-weight:400">Denotes if capacity deduplication is enabled (Nutanix AHV & VMware vSAN only)</span>
        </p>
      </td>
    </tr>
    <tr>
        <td>
            <p> <strong>Compression</strong></p>
        </td>
        <td>
        <p>
          <span style="font-weight:400">Denotes if compression is enabled (Nutanix AHV & VMware vSAN only)</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Datastore Name</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">The name of the datastore</span>
        </p>
      </td>
    </tr>
    <tr>
        <td>
            <p> <strong>Datastore Object Name</strong></p>
        </td>
        <td>
        <p>
          <span style="font-weight:400">The object UUID of the datastore</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Datastore Path</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">The network path of the datastore</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Datastore Type</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">The datastore type (underlying technology)</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Free Space</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">The amount of free space in the datastore in gigabytes</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>I/O Latency</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Storage I/O Control size-normalized I/O latency</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>IOPS</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Storage I/O Control aggregated IOPS</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Local Datastore <br>
          </strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Denotes whether the datastore is a local datastore <br>
          </span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Maintenance Mode</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Whether the datastore is currently in maintenance mode</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Max Queue Depth</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Storage I/O Control datastore maximum queue depth</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Read IOPS</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Average number of read commands issued per second to the datastore during the collection interval</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Read Latency</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">The average time a read from the datastore takes</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Read Rate</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Rate of reading data from the datastore</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>SDRS Read IOPS</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Storage DRS datastore read I/O rate</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>SDRS Read Latency</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Storage DRS datastore normalized read latency</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>SDRS Write IOPS</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Storage DRS datastore write I/O rate</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>SDRS Write Latency</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Storage DRS datastore normalized write latency</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>SIOC Active Time</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Percentage of time Storage I/O Control actively controlled datastore latency</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Storage I/O Control Enabled</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">If Storage I/O Control is enabled</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Storage Stats Collection</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Are storage statistics being collected</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Stress Level</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Stress Level is a flexible load measure which you can customize using the "Stress Settings" pane</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>vSAN Build Recommendation</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">This check detects any configuration issues in the vSAN build recommendation engine</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>vSAN Cluster Health</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">This check verifies that all ESXi hosts have the vSAN Health Service VIB installed</span>
        </p>
      </td>
    </tr>
     <tr>
      <td>
        <p>
          <strong>vSAN Congestions</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Congestions of IOs generated by all vSAN clients in the cluster</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>vSAN Data Health</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">This check provides a cluster wide overview by summarizing all objects in the cluster and categorizes object health to help you assess not only if an object is healthy or unhealthy, but what it means to the user, whether he should take action, whether he is at risk, and so on</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>vSAN Disk Configuration</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">vSAN disk configuration (Hybrid or All Flash)</span>
        </p>
      </td>
    </tr>
      <tr>
      <td>
        <p>
          <strong>vSAN Free Capacity</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">vSAN space available for new allocations.For parent folder, the value displayed belongs to the vSAN cluster with minimum free space</span>
        </p>
      </td>
    </tr>
     <tr>
      <td>
        <p>
          <strong>vSAN Hardware Compatibility Health</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">This check verifies whether the storage I/O controller firmware is compatible with the controller on the ESXi host and the version of ESXi</span>
        </p>
      </td>
    </tr>
     <tr>
      <td>
        <p>
          <strong>vSAN Health</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Summary of all vSAN health checks</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>vSAN Limits Health</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">This check looks at free disk capacity and ensures that the components per host limit has not been exceeded, and that there is some flash read cache capacity remaining</span>
        </p>
      </td>
      <tr>
      <td>
        <p>
          <strong>vSAN Network Health</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">This check tests that all ESXi hosts in a vSAN cluster have been configured so that all vSAN VMkernel NICs are on the same IP subnet</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>vSAN Online Health</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">The CEIP check verifies whether the program is enabled for your vCenter Server</span>
        </p>
      </td>
    </tr>
     <tr>
      <td>
        <p>
          <strong>vSAN Outstanding IO</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Outstanding IO from all vSAN clients in the cluster</span>
        </p>
      </td>
    </tr>
     <tr>
      <td>
        <p>
          <strong>vSAN Performance Service Health</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">This check verifies that the vSAN performance service statistics collection is working correctly</span>
        </p>
      </td>
    </tr>
     <tr>
      <td>
        <p>
          <strong>vSAN Physical Disk Health</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">This check tests whether there is an issue in retrieving the physical disk information from hosts in the vSAN cluster. If this health status is not green (OK), physical disk information cannot be retrieved from the ESXi host</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>vSAN Total System Overhead</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">vSAN capacity consumed by vSAN for system needs</span>
        </p>
      </td>
    </tr>
      <tr>
      <td>
        <p>
          <strong>vSAN Total Used - Physically Written</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">vSAN capacity storing actual data of the objects on the vSAN datastore</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>vSAN Total Used - VM Overreserved</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">vSAN space wasted due to higher than needed space reservation setting</span>
        </p>
      </td>
    </tr>
     <tr>
      <td>
        <p>
          <strong>vSAN Total Used Capacity</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">vSAN space not available for new allocations</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Write IOPS</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Average number of write commands issued per second to the datastore during the collection interval</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Write Latency</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">The average time a write to the datastore takes</span>
        </p>
      </td>
    </tr>
    <tr>
      <td>
        <p>
          <strong>Write Rate</strong>
        </p>
      </td>
      <td>
        <p>
          <span style="font-weight:400">Rate of writing data to the datastore</span>
        </p>
      </td>
    </tr>
  </tbody>
</table>