Enable additional object in NAbox 4 | NetApp | Page 1

tender sail Jul 26, 2024, 7:45 AM

#

Hi @spark krakeny I am currently trying to configure additional objects such as CIFSSession, NFSv4Pool, Vscan for Zapi and REST in NAbox 4. As described in the documentation, I have created a ZAPI and REST folder in the /etc/nabox/harvest/user/ directory and a custom.yaml. The custom.yaml is structured like the old one. But after rebooting the appliance the metrics are not being collected. Do I understand something wrong about this?
objects:
CIFSSession:
- cifs_session.yaml

and

objects:
NFSv4Pool:
- nfsv4_pool.yaml
VscanSVM:
- vscan_svm.yaml

spark kraken Jul 26, 2024, 7:49 AM

#

It shouldn’t be formatted as the old one, just regular harvest customization

#

https://nabox.org/faq/#customize-harvest

tender sail Jul 26, 2024, 8:05 AM

#

ahh I see it should look like
objects:
CIFSSession: cifs_session.yaml

and not
objects:
CIFSSession:

cifs_session.yaml

tender sail Jul 26, 2024, 8:32 AM

#

file is now adjusted and I see it in the /etc/nabox/harvest/active/zapi perf etc. folder but the metrics are not collected

blissful portal Jul 26, 2024, 8:54 AM

#

@tender sail Could you share the Harvest logs with us at ng-harvest-files@netapp.com . Log collection guide here: https://netapp.github.io/harvest/24.05/help/log-collection/#nabox

tender sail Jul 26, 2024, 9:03 AM

#

probably this need to be adjusted for NAbox 4 🙂
no such service: nabox-api
no such service: nabox-harvest2
tar (child): Cannot connect to nabox-logs-2024-07-26_09: resolve failed
tar: Child returned status 128
tar: Error is not recoverable: exiting now

spark kraken Jul 26, 2024, 10:05 AM

#

You can collect a support bundle in NAbox and send to to this email

tender sail Jul 26, 2024, 11:15 AM

#

@blissful portal log bundle is to big for the mailserver. Is it ok when I send you a S3 download link?

blissful portal Jul 26, 2024, 11:19 AM

#

Can you upload the files via this site?
https://upload.nabox.org/app/share/7d2FYc4DB26-xnXKzxkvYeq-Puvw4T2v32M-HzbcttY6qeu

tender sail Jul 26, 2024, 11:21 AM

#

done

blissful portal Jul 26, 2024, 11:23 AM

#

Received !!

blissful portal Jul 26, 2024, 11:41 AM

#

Could you confirm that the folder ~./harvest/active/zapi/cdot/9.8.0 has the cifs_session.yaml file ?

Because there are all files mentioned inn logs as below but this file:

Jul 26 08:28:17 xxxxx-1 dc[1455]: havrest           | 2024-07-26T08:28:17Z INF collector/helpers.go:88 > best-fit template Poller=xxxxx collector=Zapi:SecurityLogin path=/harvest/conf/zapi/cdot/9.8.0/security_login.yaml v=9.13.1
Jul 26 08:28:17 xxxx-1 dc[1455]: havrest           | 2024-07-26T08:28:17Z INF collector/helpers.go:88 > best-fit template Poller=xxxxx collector=Zapi:Volume path=/harvest/conf/zapi/cdot/9.8.0/volume.yaml v=9.13.1
Jul 26 08:28:17 xxxxx-1 dc[1455]: havrest           | 2024-07-26T08:28:17Z INF collector/helpers.go:88 > best-fit template Poller=xxxxx collector=Zapi:Volume path=/harvest-conf/active/zapi/cdot/9.8.0/exclude_transient_volumes.yaml v=9.13.1
Jul 26 08:28:17 xxxxx-1 dc[1455]: havrest           | 2024-07-26T08:28:17Z INF collector/helpers.go:88 > best-fit template Poller=xxxxx collector=Zapi:SnapMirror path=/harvest/conf/zapi/cdot/9.8.0/snapmirror.yaml v=9.13.1
Jul 26 08:28:18 xxxxx-1 dc[1455]: havrest           | 2024-07-26T08:28:18Z INF collector/helpers.go:88 > best-fit template Poller=xxxx collector=Zapi:SnapshotPolicy path=/harvest/conf/zapi/cdot/9.8.0/snapshotpolicy.yaml v=9.13.1

tender sail Jul 26, 2024, 11:46 AM

#

I see, in that folder is only the exclude_transient_volumes.yaml file

tender sail Jul 26, 2024, 12:04 PM

#

so that means for the "non" standard default.yaml I need to build up the structure for the specific objects in the user directory

blissful portal Jul 26, 2024, 12:23 PM

#

Yes, Changes should be performed in /etc/nabox/harvest/user/ folder to avoid overwritten when upgrading Harvest. Reference: https://nabox.org/faq/#customize-harvest

tender sail Jul 26, 2024, 12:31 PM

#

makes absolute sense, but for me it was not so clear that this also applies to files like cifs_session.yaml wich is already there. I thought this is only counts for own written files

#

I've now created the path and file in the user folder

#

hm doest not look better. Just uploaded the new bundle

serene ivy Jul 26, 2024, 1:32 PM

#

hi @tender sail can you try this.

cat /etc/nabox/harvest/user/rest/custom.yaml

objects:
  CIFSSession:                 cifs_session.yaml

With that configuration, after dc restart havrest, I see the template loaded and used

2024-07-26T13:24:27Z INF collector/helpers.go:88 > best-fit template Poller=ntap-01 collector=Rest:CIFSSession path=/harvest/conf/rest/9.8.0/cifs_session.yaml v=9.14.1

tender sail Jul 29, 2024, 6:29 AM

#

Hi @serene ivy thank you very much, now it looks better.But I dont get it what did I wrong

serene ivy Jul 29, 2024, 11:55 AM

#

@tender sail glad that worked for you! In terms of why it didn't work earlier, not 100% sure what you had before. Was it identical to what I shared above?

tender sail Jul 29, 2024, 12:25 PM

#

I was a bit confused how it should be implemented, a typical moment of PEBCAK. I was not aware that for example the cifs_session.yaml with the whole path need to be created in the /etc/nabox/harvest/user and I also created thee custom_<xyz>.yaml file instead another custom.yaml

spark kraken Jul 29, 2024, 12:39 PM

#

mmm. I don't think it needs to be created

serene ivy Jul 29, 2024, 12:40 PM

#

right, in the example I pasted above - it was not created. The custom.yaml enables it and Harvest uses the cifs_session.yaml that ships out-of-the-box

tender sail Jul 29, 2024, 2:13 PM

#

ok then it is clear for me. Every conf which is out of the box does not to be recreated. Only the custom.yaml in the user folder needs to be created or extended

serene ivy Jul 29, 2024, 3:09 PM

#

With the additional nuisance that REST templates do not have a way to extend them like ZAPI templates. In other words, ZAPI templates can be extended by creating a new template that will be merged with the out-of-the-box template. REST templates do not support merging, which means if you want to modify one of the out-of-the-box REST templates you need to create a copy of the original, modify it, and use a custom.yaml to use your new copy. https://netapp.github.io/harvest/nightly/configure-templates/#extend-an-existing-object-template

In your case, @tender sail you did not want to extend a template, you wanted to use a disabled-by-default template, which requires only creating a custom.yaml that references the out-of-the-box template

tender sail Jul 30, 2024, 8:13 AM

#

I see would it be possible to add this to the documentation, how to enable "disabled-by-default" templates?

#Enable additional object in NAbox 4