Solved

Get-NTNXHostStat - Where can I find the specfics on the required -metrics argument?

  • 11 September 2019
  • 1 reply
  • 1013 views

Userlevel 1
Badge +3
Working with the NTNX Powershell cmdlets and struggling to find information regarding the required -metrics argument for the Get-NTNXHostStat cmdlet. Where can the metrics be found?
icon

Best answer by McCranium 11 September 2019, 22:13

View original

This topic has been closed for comments

1 reply

Userlevel 1
Badge +3
And for those who are interested, I figured out a way to get the metrics:

The metrics appear to be the same as the stats on the host. This really should've been more simple to find in the documentation though. You can see that the metrics that Chandru referenced "hypervisor_memory_usage_ppm" is available in the list below.


The metrics appear to be the same as the stats on the host. This really should've been more simple to find in the documentation though. You can see that the metrics that Chandru referenced "hypervisor_memory_usage_ppm" is available in the list below.


$NTXSvr = Get-NTNXHost
$NTXSvr[0].stats

Here's the resultant list:

Key Value
--- -----
hypervisor_avg_io_latency_usecs 0
num_read_iops 480
$NTXSvr[0].stats

Here's the resultant list:

Key Value
--- -----
hypervisor_avg_io_latency_usecs 0
num_read_iops 480
hypervisor_write_io_bandwidth_kBps 0
timespan_usecs 20000000
controller_num_read_iops 419
read_io_ppm 843500
controller_num_iops 668
total_read_io_time_usecs -1
controller_total_read_io_time_usecs 21530657
hypervisor_num_io 0
controller_total_transformed_usage_bytes -1
hypervisor_cpu_usage_ppm 207203
controller_num_write_io 4987
avg_read_io_latency_usecs -1
content_cache_logical_ssd_usage_bytes 0
controller_total_io_time_usecs 33110993
controller_total_read_io_size_kbytes 268115
controller_num_seq_io -1
controller_read_io_ppm 627223
content_cache_num_lookups 78679
controller_total_io_size_kbytes 522571
content_cache_hit_ppm 410770
controller_num_io 13378
hypervisor_avg_read_io_latency_usecs 0
content_cache_num_dedup_ref_count_pph 100
num_write_iops 89
controller_num_random_io 0
num_iops 569
hypervisor_num_read_io 0
hypervisor_total_read_io_time_usecs 0
controller_avg_io_latency_usecs 2475
num_io 11393
controller_num_read_io 8391
hypervisor_num_write_io 0
controller_seq_io_ppm -1
controller_read_io_bandwidth_kBps 13405
controller_io_bandwidth_kBps 26128
hypervisor_num_received_bytes 0
hypervisor_timespan_usecs 29861007
hypervisor_num_write_iops 0
total_read_io_size_kbytes 80848
hypervisor_total_io_size_kbytes 0
avg_io_latency_usecs 196
hypervisor_num_read_iops 0
content_cache_saved_ssd_usage_bytes 0
controller_write_io_bandwidth_kBps 12722
controller_write_io_ppm 372776
hypervisor_avg_write_io_latency_usecs 0
hypervisor_num_transmitted_bytes 0
hypervisor_total_read_io_size_kbytes 0
read_io_bandwidth_kBps 4042
hypervisor_memory_usage_ppm 351338
hypervisor_num_iops 0
hypervisor_io_bandwidth_kBps 0
controller_num_write_iops 249
total_io_time_usecs 2242417
content_cache_physical_ssd_usage_bytes 0
controller_random_io_ppm -1
controller_avg_read_io_size_kbytes 31
total_transformed_usage_bytes -1
avg_write_io_latency_usecs -1
num_read_io 9610
write_io_bandwidth_kBps 6075
hypervisor_read_io_bandwidth_kBps 0
random_io_ppm -1
total_untransformed_usage_bytes -1
hypervisor_total_io_time_usecs 0
num_random_io -1
controller_avg_write_io_size_kbytes 51
controller_avg_read_io_latency_usecs 2565
num_write_io 1783
total_io_size_kbytes 202356
io_bandwidth_kBps 10117
content_cache_physical_memory_usage_bytes 6366663580
controller_timespan_usecs 20000000
num_seq_io -1
content_cache_saved_memory_usage_bytes 0
seq_io_ppm -1
write_io_ppm 156499
controller_avg_write_io_latency_usecs 2322
content_cache_logical_memory_usage_bytes 6366663580