#Missing metric data after Harvest upgrade

1 messages · Page 1 of 1 (latest)

hazy sky
#

After upgrading Harvest in NABOX, I'm no longer receiving data for volume_space_logical_available. Where do I begin to troubleshoot?

proud sail
#

Double check the roles required by harvest, they change over time

final plover
#

@hazy sky Could you share your ONTAP version? Also, do you see any data returned for this field when you run the query below?

volume show -fields logical-available
hazy sky
hazy sky
final plover
#

Okay, Could you confirm if you are using Rest or Zapi collector?

final plover
hazy sky
final plover
#

Not more than 5 mins

hazy sky
final plover
#

Do you see other volume metrics like volume_space_logical_used for this Cluster?

final plover
#

If you query below endpoint
https://CLUSTER_IP/api/private/cli/volume?fields=logical-available
Do you get this field?
Also what is the output of below command in nabox?

dc exec nabox-harvest2 grep -r 'logical-available' /conf
final plover
#

Are there any errors in below command

dc logs nabox-harvest2 2>&1 | grep -w 'Rest:Volume'
hazy sky
#

Just for reference, this was working prior to the Harvest upgrade.

final plover
#

Okay, with which version of Harvest did it work?

hazy sky
final plover
#

Thanks. We ll check on our end.

hollow hollow
#

Thanks @hazy sky for raising this issue. With your help, we found the problem and fixed in https://github.com/NetApp/harvest/pull/2943
We can explain how to edit the template locally or you can install a new nightly build once that build passes CI. Let us know which you prefer

hazy sky
final plover
#
  1. SSH as root to nabox:

  2. Change the directory to /opt/harvest2-conf/conf/rest/9.12.0:

     ```sh
    

    cd /opt/harvest2-conf/conf/rest/9.12.0

    
    
  3. Open the volume.yaml file with vi editor:

      ```sh
    

    vi volume.yaml

    
    
  4. At line 33, Change the string logical-available to logical_available.

  5. Restart nabox:

      ```sh
    

    dc restart

hazy sky
hollow hollow
#

The gist of which is create a custom_volume_fix.yaml file, copy the existing volume.yaml to custom_volume.yaml, make your edits to the custom_volume.yaml file, update custom_volume_fix.yaml to point to the new custom_volume.yaml and then dc restart

hazy sky