Subscribe

Unable to get system counter info for sys_avg_latency when using apitest.exe

[ Edited ]

Hi,

 

 

I am trying to get the "sys_avg_latency" counter-name for object-type "system" using apitest and I am unable to get the counter values.  I am able to get the

 

 

counter values for "avg_processor_busy".  IS there an extra parameter I should put in the input xml? Or is this counter not available thru the DFM?  Please advise.

 

The input xml (perf3.xml):

 

<perf-get-counter-data>

<instance-counter-info>

<counter-info>

<perf-object-counter>

<counter-name>sys_avg_latency</counter-name>

<object-type>system</object-type>

</perf-object-counter>

</counter-info>

<object-name-or-id>172.17.39.164</object-name-or-id>

</instance-counter-info>

</perf-get-counter-data>

 

COMMAND:

 

apitest.exe -I -t dfm 172.17.38.144 root Netapp123 < perf3.xml

 

<results status="passed">

        <perf-instances>

                <perf-instance-counter-data>

                        <instance-name>system</instance-name>

                        <object-id>222</object-id>

                        <counters>

                                <perf-counter-data>

                                        <object-type>system</object-type>

 

                                        <counter-name>sys_avg_latency</counter-name>

 

                                        <label-names/>

                                        <unit>millisec</unit>

                                        <counter-data/>

                                </perf-counter-data>

                        </counters>

                </perf-instance-counter-data>

        </perf-instances>

</results>

rle Former NetApp Employee

Re: Unable to get system counter info for sys_avg_latency when using apitest.exe

Hi Agnes -

I would use perf-object-counter-list-info to obtain a valid list of counters for the system object.

Regards,

   - Rick -

Re: Unable to get system counter info for sys_avg_latency when using apitest.exe

Hi,

Yes, I have tried it and sample output does include sys_avg_latency as a valid counter.  The input.xml is as follows:

<perf-object-counter-list-info>

<object-name>system</object-name>

</perf-object-counter-list-info>

Here is a snippet of the output  and attached is the entire output from getting perf-object-counter-list-info for "system":

               <perf-counter>

                       <desc>Average latency for all operations in the system in milliseconds</desc>

                       <name>sys_avg_latency</name>

                       <properties>average</properties>

                       <is-display>true</is-display>

                       <unit>millisec</unit>

                       <privilege-level>basic</privilege-level>

                       <base-counter>total_ops</base-counter>

               </perf-counter>

Please advise if there something I need to add to the input.xml to get the counter values for "sys_avg_latency"

Re: Unable to get system counter info for sys_avg_latency when using apitest.exe

Hi Agnes,

Which version of DFM are you using?

I am using DFM 5.0.1.

Calling perf-object-counter-list-info for system indicates that there is no  sys_avg_latency counter. Hence it is not a valid counter.

Re: Unable to get system counter info for sys_avg_latency when using apitest.exe

The sys_avg_latency is dependent on total_ops.

Try running this as input to your DFM.

<perf-get-counter-dependents>

    <counters>

      <perf-object-counter>

        <counter-description></counter-description>

        <counter-name>total_ops</counter-name>

        <is-calculated-stats></is-calculated-stats>

        <object-type>system</object-type>

      </perf-object-counter>

    </counters>

  </perf-get-counter-dependents>

The output i got was :

<results status='passed'>

                    <dependent-counters>

                              <perf-object-counter>

                                        <counter-name>sys_avg_latency</counter-name>

                                        <object-type>system</object-type>

<is-calculated-stats>false</is-calculated-stats>

                              </perf-object-counter>

                    </dependent-counters>

                    <base-counters/>

                    <reports/>

                    <views/>

                    <threshold-templates/>

                    <thresholds/>

          </results>