Skip navigation
44,099 Views 3 Replies Last post: Nov 20, 2009 10:58 AM by kvishal RSS
pdion@expedia.com Novice 2 posts since
May 13, 2008
Currently Being Moderated

May 15, 2008 12:24 PM

Ontap API  Performance monitoring: perf-object-get-instances  parameters not consider.

 

Hi,

 

 

I recently begin to work on Netapp API to gather Performance monitoring using Perl Ontap API 3.0. I look the  perf_operation.pl which is quite complete !

 

 

But, I'm looking for a script that can get Per instances performance stats, per example, let say that I would like to query avg_latency for a specific Volume. Following the documentation  I should use the API perf-object-get-instances and include parameters such as this example  using the Windows command line tool:

 

 

manage-ontap-sdk-3.0\bin\nt>apitest.exe netapp01 <USER> <PASSWORD> perf-object-get-instances objectname volume instances vol0 counters avg_latency

 

 

The problem here is that the output of the command is ALL counters for All volumes on the filer. I also try this API using Perl and  zeplorer.exe; they all ignore instances and counters inputs.

 

 

 

 

 

Any idea ? Could it be a API bug ?

 

 

 

 

 

Thanks a lot.

 

 

 

 

 

 

 

 

nagendrk NetApp Employee Community Moderator Virtuoso 245 posts since
Mar 29, 2008

 

I see a similar behavior..  May be its a bug !

 

 

 

 

 

I could code around the problem and enhance the perf_operation.pl script to do what you are asking, that is, to query a counter value for a particular volume.  Try the attached script. 

 

 

Syntax :

 

 

C:\perl>perf_operation.pl <filer> <user> <pwd> get-instance-counter-value  <object>  <instance>  <counter>

 

 

For eg.

 

 

C:\perl>perf_operation.pl <filer> <user> <pwd> get-instance-counter-value  volume  vol0  avg_latency

 

 

Attachments:
Ashitkumar Enthusiast 4 posts since
May 27, 2008

I face the same issue with the CPP SDK. Is there any fix available?

I am using SDK 3.0.

 

--Ashit

kvishal NetApp Employee Master 111 posts since
Jul 28, 2009

I dont think there is a fix available. It is a API bug and not dependent on SDK version or langauge used

More Like This

  • Retrieving data ...

Bookmarked By (0)