NetworkIn- NetworkOut-
bound(M) bound(M)
—————————————-————————-—————-————-—————
savdalfs01 113 2352 2352 2352 261128 2206 3478
Also shown is disk information related to IOPS, latency, and read and write
information, but there are also cryptic values related to HardDiskMetrics and
NetworkMeteredTrafficReport, which don’t actually give any useful information. Each
of those entries are separate reports that have to be viewed as specific report entities.
You do this by saving the metering to a variable and then inspecting the separate
report elements. If you look at the storage report for Windows Server 2012 R2, you
would not see the normalized I/O count, as this is new to Windows Server 2016. Also
remember that when using the new Windows Server 2016 Storage QoS, additional
metrics are available, as covered in Chapter 4. Here is an example of the basic
metering output for networking and storage:
PS C:> $report = Measure‐VM ‐VMName savdalfs01
PS C:> $report.NetworkMeteredTrafficReport
LocalAddress RemoteAddress Direction TotalTraffic(M)
————————————-————-———————-
0.0.0.0/0 Inbound 2121
0.0.0.0/0 Outbound 3479
::/0 Inbound 88
::/0 Outbound 2
PS C:> $report.HardDiskMetrics
VirtualHardDisk : HardDiskDrive (Name = 'Hard Drive on SCSI
controller number 0 at location 0', VMName =
'VM1') [Id = 'Microsoft:6C79B7C6–13CB-4E22-B528–
870F92A8D373\7E4A44C7-C488–4E8F-9588–8D3699
252C9B\0\0\D', VMId = '6c79b7c6–13cb-4e22-b528–
870f92a8d373']
AverageNormalizedIOPS: 41
AverageLatency : 1915
DataRead : 409
DataWritten : 79
NormalizedIOCount : 68626
VirtualHardDisk : HardDiskDrive (Name = 'Hard Drive on SCSI
controller number 0 at location 1', VMName =
'VM1') [Id = 'Microsoft:6C79B7C6–13CB-4E22-B528–
870F92A8D373\7E4A44C7-C488–4E8F-9588–8D3699
252C9B\0\1\D', VMId = '6c79b7c6–13cb-4e22-b528–
870f92a8d373']
AverageNormalizedIOPS: 0
AverageLatency : 0
DataRead : 1
DataWritten : 0
NormalizedIOCount: 18
The resource-metering functionality gives a great view into the metrics of a single