Volume workload still showing in nabox with QoS disabled

[topaz spruce]

I have a single volume that is showing up in ONTAP:Workload which is odd and I'm just trying to clean things up. It did have the value-fixed QoS policy set. I unchecked "Enforce Performance Limits" on the volume and it seemed like nabox stopped collecting for a little bit, but then it started back up collecting on that volume again. Qos policy-group show and qos adaptive show zeros in the columns for WkIds so nothing is set up for QoS. Anyone have an idea as to why this one volume is still showing up in nabox - ONTAP:Workload?

[marble peak]

@topaz spruce
Harvest collects all workloads where user-defined, system-defined and autovolume workload classes are applied. If you run the CLI commands below, the Workload Class should be autovolume, and the Policy Group Name could be User-Best_Effort. This is why Harvest is tracking the stats for this workload. All autovolume workload class types are collected via the template workload_volume.yaml (https://github.com/NetApp/harvest/blob/main/conf/zapiperf/default.yaml#L66). If you prefer not to collect such data, you can disable this template.

qos workload show -workload ITEP_tst_k8s-wid30628

qos policy-group show -policy-group User-Best-Effort

[topaz spruce]

Thanks Rahul for that info. I checked on it today and it seems to have stopped collecting on that volume. Not sure why it took a while for the collection to stop after the volume's qos group policy was removed 🤷‍♂️ . I had a similar issues with an s3 bucket on another cluster and removing QoS from that seems to have done the trick as well.