-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instance level filtering for the "workload_volume.yaml" #2559
Comments
The same filtering could be applied on the similar templates ,which will help reducing the resource utilization. |
|
|
Thanks @debbrata-netapp Given that RestPerf collector support is available for ONTAP version 9.12+, We'll focus on filter support for the ZapiPerf Collector for this issue. The filter support for RestPerf is being tracked separately under issue #2534. We'll aim to provide filtering capabilities in line with those provided by ONTAP performance ZAPIs. |
@debbrata-netapp This feature is now available through the nightly builds. The documentation can be found here, and the steps for NABox are provided here. |
Tested in main with commit 503b460 Validation for workload_detail ZapiPerf template
Added filter in workload_detail ZapiPerf template
Validation for Lun ZapiPerf template
Added filter in Lun ZapiPerf template
|
Is your feature request related to a problem? Please describe.
Customer's requirement is to monitor latency for few critical volumes out of many at a granular level like , per 5-sec.
With this available template we would end up polling data from a system which contains 1000+ of volumes , which is not required for customer. With the existing template we would end up in unnecessary polling and data size is also large , especially for large systems.
Describe the solution you'd like
An instance level polling/filtering can reduce the excessive polling.
This will reduce the CPU pressure and the data set is much smaller for customer to retain historical information for a longer duration.
Describe alternatives you've considered
NA
Additional context
NA
The text was updated successfully, but these errors were encountered: