2011-08-03 02:12 PM
This question is in reference to the following thread: http://communities.netapp.com/message/47302#47302
From the prior discussion the main conclusion was that thresholds could not be set on some counters (especially, it would seem, diag mode counters) because they are label counters.
Solved! SEE THE SOLUTION
2011-08-03 09:02 PM
Please follow the answer of your questions:
1. What is meant by the term label counter in regards to Performance Advisor?
Labels give more granular information about counters. A label is an additional prefix added after a Performance Advisor counter name to specify an operation related that counter. Labels with counters are of the form: countername:label1:label2 For one-dimensional arrays only label1 is used while for two-dimensional arrays, label2 is also used. Some 2-dimensional counters, are:
2. What process or command can you use to determine which counters are label counters?
Use this dfm command to get the information of label counter
$ dfm perf counter list <storage_system id>:<object_type>:*:*:*:*
For example in my dfm server, the host id of the storage system is 94 so I have executed the following command to get the label info for the object type "processor".
$dfm perf counter list 94:processor:*:*:*:*
Object Instance Counter Label1 Label2 Unit Priv
------- --------- -------- ------- ------- ----- -----
processor processor1 processor_busy percent basic
processor processor1 processor_elapsed_time none basic
processor processor0 processor_busy percent basic
processor processor0 processor_elapsed_time none basic
Here processor object type does not have any applicable label counter, that's why it does not print label info.
You can specify the countername also here in this cli like
$dfm perf counter list 94:processor:processor_busy:*:*:*
For better usage of this dfm CLI, execute the command
$ dfm perf counter list help