Skip to main content
NetApp Knowledge Base

How to view full volume or workload names truncated in ONTAP qos statistics output

Views:
3,910
Visibility:
Public
Votes:
2
Category:
ontap-9
Specialty:
perf
Last Updated:

Applies to

  • ONTAP 9

Description

  • Long volume and workload names are truncated in `qos statistics` output, and the shortened names end in `..`
  • Affected commands include:
    • qos statistics volume latency show
      qos statistics volume performance show
      qos statistics workload latency show
      qos statistics workload performance show
  • Volumes with a common prefix look identical, so it isn't clear which volume has the high latency or IOPS

Example:

cluster::> qos statistics volume latency show
Workload            ID    Latency    Network    Cluster       Data       Disk        QoS      NVRAM      Cloud
--------------- ------ ---------- ---------- ---------- ---------- ---------- ---------- ---------- ----------
-total-              -    17.35ms    14.14ms    60.00us  1106.00us     2.04ms        0ms        0ms        0ms
vol_database_..  12345      2.40s      1.72s     1.00us   141.69ms   535.44ms        0ms        0ms        0ms
vol_database_..  12346      1.59s      1.52s        0ms     4.52ms    61.90ms        0ms        0ms        0ms

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.