Name: CommonStat

In order to give flexibility in terms which attributes are present in the Slice instance and which are not; all attributes are defined as Number Wrapper Objects (Integer or Double) rather than primitive types (int or double). So when an object does not have a value for an attribute, it will be 'null object reference' which is expected to be excluded in JSON representation of this object on the wire. Essentially that helps us to use the same CommonSlice to send any arbitrary set of attribute values in a given slice. If we need to set a default value for an attribute, primitives help; but same can be achieved by explicitly setting value of that attribute using Integer or Double instance of that value.

Data Structure
{
   "typeId": "com.tintri.api.rest.v310.dto.domain.beans.perf.CommonStat",
   "cloneDedupeFactor": <Number>,
   "compressedSpaceUsedLive": <Number>,
   "compressedSpaceUsedSnapshotOnly": <Number>,
   "compressionFactor": <Number>,
   "flashHitPercent": <Number>,
   "intervalSeconds": <Number>,
   "ioAlignedPercent": <Number>,
   "latencyContentionMs": <Number>,
   "latencyDifferenceFromMaxInSetMs": <Number>,
   "latencyDiskMs": <Number>,
   "latencyFlashMs": <Number>,
   "latencyHostMs": <Number>,
   "latencyIopsPercent": <Number>,
   "latencyMirrorMs": <Number>,
   "latencyMirrorReadMs": <Number>,
   "latencyMirrorWriteMs": <Number>,
   "latencyMirrorWriteNetworkMs": <Number>,
   "latencyNetworkMs": <Number>,
   "latencyStorageMs": <Number>,
   "latencyThrottleMs": <Number>,
   "latencyTotalMs": <Number>,
   "liveLogicalFootprint": <Number>,
   "normalizedTotalIops": <Number>,
   "operationsReadIops": <Number>,
   "operationsTotalIops": <Number>,
   "operationsWriteIops": <Number>,
   "performanceReserveActual": <Number>,
   "performanceReserveAutoAllocated": <Number>,
   "performanceReserveChange": <Number>,
   "performanceReserveChangePercent": <Number>,
   "performanceReserveIfAutoAllocated": <Number>,
   "performanceReserveIfPinned": <Number>,
   "performanceReservePinned": <Number>,
   "performanceReserveRemaining": <Number>,
   "performanceReserveUsed": <Number>,
   "spaceProvisionedGiB": <Number>,
   "spaceSavingsFactor": <Number>,
   "spaceUsedChangeGiB": <Number>,
   "spaceUsedChangePercent": <Number>,
   "spaceUsedChangePhysicalGiB": <Number>,
   "spaceUsedDifferenceFromMaxInSetGiB": <Number>,
   "spaceUsedDifferenceFromMaxInSetPhysicalGiB": <Number>,
   "spaceUsedGiB": <Number>,
   "spaceUsedLiveGiB": <Number>,
   "spaceUsedLivePhysicalGiB": <Number>,
   "spaceUsedPhysicalChangePercent": <Number>,
   "spaceUsedPhysicalGiB": <Number>,
   "spaceUsedSnapshotsHypervisorGiB": <Number>,
   "spaceUsedSnapshotsHypervisorPhysicalGiB": <Number>,
   "spaceUsedSnapshotsTintriGiB": <Number>,
   "spaceUsedSnapshotsTintriPhysicalGiB": <Number>,
   "throughputCacheReadMBps": <Number>,
   "throughputFlashMissMBps": <Number>,
   "throughputReadMBps": <Number>,
   "throughputTotalMBps": <Number>,
   "throughputWriteMBps": <Number>,
   "timeEnd": DateTime,
   "timeStart": DateTime,
   "requestSizeKiB": <Number>,
   "uuid": Uuid,
}

Elements
NameTypeDescription
requestSizeKiBxsd:doublehelper derive average request size from mbps and iops
uuidUuidUUID of the VM or VDisk to which this performance sample corresponds.

Attributes
NameTypeDescription
cloneDedupeFactorxsd:doubleMeasure of the space saved due to deduplication from Tintri clones. This is computed as a ratio of the logical footprint and the logical bytes written, before block deduplication (if applicable). A value of 1.0 means no savings due to clone deduplication. Higher values mean greater space savings. This field is being deprecated at the VM and vDisk levels. We recommend using the spaceSavingsFactor at the VM and vDisk levels instead.
compressedSpaceUsedLivexsd:doubleLogical size of Live VM data (does not include snapshots) after compression. This attribute is not returned for the DatastoreStat since it is only available at the VM and vDisk levels.
compressedSpaceUsedSnapshotOnlyxsd:doubleLogical size of data captured only in snapshots of the VM, after compression. This attribute is not returned for the DatastoreStat since it is only available at the VM/vDisk level.
compressionFactorxsd:doubleAt the datastore level, this is a measure of the space saved due to compression, and is computed as a ratio of the logical bytes stored and the physical space used. At the VM and vDisk levels, this is a measure of the compressibility of the data written to the VM or vDisk, and is computed as a ratio of the logical written size and the compressed space used. A value of 1.0 means no savings due to compression. Higher values mean greater space savings.
flashHitPercentxsd:doubleThe percentage of all reads and writes that are satisfied by flash storage.
intervalSecondsxsd:longThe interval between datapoints in seconds
ioAlignedPercentxsd:doublePercentage of read and written bytes that is aligned.
latencyContentionMsxsd:doubleThe portion of overall latency contributed by QoS contention
latencyDifferenceFromMaxInSetMsxsd:doubleThe difference between the sum of the total vDisks or VMs max host or network latency and a single vDisk or VM
latencyDiskMsxsd:doubleThe portion of overall latency contributed by the hard disks in milliseconds.
latencyFlashMsxsd:doubleThe portion of overall latency contributed by QoS flash
latencyHostMsxsd:doubleThe portion of overall latency contributed by from ESX hosts down to disks in milliseconds.
latencyIopsPercentxsd:doubleThe percentage of total latency due to host and network latency.
latencyMirrorMsxsd:doubleThe portion of latency (read and write) contributed by synchronous replication (transparent failover).
latencyMirrorReadMsxsd:doubleThe portion of read latency contributed by synchronous replication (transparent failover).
latencyMirrorWriteMsxsd:doubleThe portion of write latency (including network) contributed by synchronous replication (transparent failover).
latencyMirrorWriteNetworkMsxsd:doubleThe portion of network latency contributed by synchronous replication (transparent failover).
latencyNetworkMsxsd:doubleThe portion of overall latency contributed by from the network down to disks in milliseconds.
latencyStorageMsxsd:doubleThe portion of overall latency contributed by the Tintri storage in milliseconds. It includes latency of disks.
latencyThrottleMsxsd:doubleThe portion of overall latency contributed by QoS throttling
latencyTotalMsxsd:doubleThe maximum host and network latency in milliseconds.
liveLogicalFootprintxsd:doubleThe logical size of the live VM (snapshot-only space not included) before space savings. This is the amount of space needed for the live VM if it were migrated to storage without space savings. This stat is reported at the VM and vDisk levels
normalizedTotalIopsxsd:intNormalized Read and Write IOPS total
operationsReadIopsxsd:intRead operations per second.
operationsTotalIopsxsd:longTotal IOPS on the datastore.
operationsWriteIopsxsd:intWrite operations per second.
performanceReserveActualxsd:doublePerformance reserve percent.
performanceReserveAutoAllocatedxsd:doublePerformance reserve percentage for a disk or VM.
performanceReserveChangexsd:doublePercentage value of change over last 7 days.
performanceReserveChangePercentxsd:doublePercentage value of change over last 7 days.
performanceReserveIfAutoAllocatedxsd:doublePerformance reserve percentage for a disk or VM if it were auto allocated
performanceReserveIfPinnedxsd:doublePerformance reserves for a disk or VM, if it were pinned.
performanceReservePinnedxsd:doublePerformance reserves for a disk or VM.
performanceReserveRemainingxsd:doubleThe percentage of performance reserves remaining. (100 - performanceReserveUsed)
performanceReserveUsedxsd:doubleThe percentage of performance reserves used. (autoAllocatedPerfReservePercentage + pinnedPerfReservePercentage)
spaceProvisionedGiBxsd:doubleLogical space allocated on the datastore in GiB.
spaceSavingsFactorxsd:doubleMeasures the space saved due to all space savings techniques supported, excluding thin provisioning. At the VM and vDisk level, the space savings factor applies to the data written to the VM or vDisk. At the Datastore level, the space savings applies to the logical footprint of the datastore, which includes the data written to the datastore as well as the additional data accessible to clones due to clone deduplication.
spaceUsedChangeGiBxsd:doubleLive logical bytes minus the start data point live logical bytes in GiB. Change in total logial space usage in last 7 days.
spaceUsedChangePercentxsd:doublePercentage of change of the logical space used on the datastore.
spaceUsedChangePhysicalGiBxsd:doubleLive physical bytes minus the start data point live physical bytes in GiB. Change in total physical space usage in last 7 days.
spaceUsedDifferenceFromMaxInSetGiBxsd:doubleThe difference between this samples logical space used and the maximum space used in the set in GiB.
spaceUsedDifferenceFromMaxInSetPhysicalGiBxsd:doubleThe difference between this samples physical space used and the max space used in the set in GiB.
spaceUsedGiBxsd:doubleThe amount of logical space used on the datastore in GiB.
spaceUsedLiveGiBxsd:doubleLogical space used for live VM data and hypervisor snapshots in GiB (does not include snapshot-only space). Includes vDisk files and swap files.
spaceUsedLivePhysicalGiBxsd:doublePhysical (actual) space used by live VM data and hypervisor snapshots, after all space savings techniques are applied.
spaceUsedPhysicalChangePercentxsd:doublePercentage of change of the physical space used on the datastore.
spaceUsedPhysicalGiBxsd:doubleThe amount of physical space used on the datastore in GiB.
spaceUsedSnapshotsHypervisorGiBxsd:doubleLogical space used for hypervisor snapshots in GiB.
spaceUsedSnapshotsHypervisorPhysicalGiBxsd:doublePhysical space used for hypervisor snapshots in GiB.
spaceUsedSnapshotsTintriGiBxsd:doubleSpace used for Tintri Snapshots in GiB.
spaceUsedSnapshotsTintriPhysicalGiBxsd:doubleActual space consumed by Tintri snapshots in GiB.
throughputCacheReadMBpsxsd:doubleThe cache read throughput that is satisfied by flash storage.
throughputFlashMissMBpsxsd:doubleSystem wide flash miss rate based on throughput in MBps. (The amount of read traffic that goes to disk)
throughputReadMBpsxsd:doubleBandwidth in MB per second for read operations.
throughputTotalMBpsxsd:doubleTotal throughput on the datastore in MBps.
throughputWriteMBpsxsd:doubleBandwidth in MB per second for write operations.
timeEndDateTimeThe end time of the interval.
timeStartDateTimeThe start time of the interval.