I'm not sure if that s helpful to me. I'm planning to poll filer on 1 sec interval, and to get information if CP is performed in that interval and which type (and maybe CP util). That's something similar to sysstat command output.
Sorry for my cDOT assumption. I don't have a 7-mode system handy.
Polling the filer every 1 second is a burden on ONTAP. Sysstat can get away with it, because it it internal to ONTAP, and even then, it is not a great idea for the long term. API calls run through the ZAPI daemon and have to process the request, call the appropriate API, and then return information. It is more work than sysstat.
If you are still interested in perusing 7-mode APIs, the perf APIs are very similar in 7-mode and cDOT.
I already do calculations to get average CPU, any CPU, disk util etc. But, for that in formations, I know which counters to poll, and do some calculations after that. For CP type and util, I don't even know which object to look for appropriate counters.
That's exactly what I want. But I have one problem now because I created low privileged user for only purpose to poll counters via script. It appears that low privileged user can't poll counters for an object that has privilege-level=admin, like wafl object, because I don't get any output, and errors are also not present.
What privilege should be added to poll user to make this possible?
Now that we know what you want, I think you can use the perf APIs to obtain what you want.
The counter object is wafl.
The counter is cp_count. The description is interesting: "Array of counts of different types of CPs"
The cp_count counter is a type delta. There is also cp_phase_times counter. I would do a perf-object-instace-list-info with the object name wafl and see what instances are available. I'm hoping that the instance names will match the ones that Chris pointed out.
If that doesn't work, you can look for various counters that are similar like wafl_bufs_available_for_cp.
<!-- Output of perf-object-get-instances-iter-start [Execution Time: 94 ms] -->
<results errno='13001' reason='Not enough memory to get instances for wafl.Use perf-object-get-instances-iter-* calls and/or ask for specific counters to limit the amount of data retrieved' status='failed'/>
If I specify instance and object everything is just fine. Thanks a lot, I'll make your answer correct.
The error message you observed is due to some changes in DOT that were introduced in 8.1.3 that is most commonly hit when using Performance Advisor. But, if you call the APIs directly you can hit the same. Here is a support announcement about it that includes links to the related bugs: