#node tagging

1 messages · Page 1 of 1 (latest)

plucky sinew
ruby jacinth
#

interesting, I don't think we have that used in many places because ours is quite extensive and has more than just the physical location

plucky sinew
#

Okay. Given it's a text field so we can fill in more details as needed and then harvest can parse it. Do you think, you can make use of this field for your use case?

ruby jacinth
#

does it collect 'owner' information?

plucky sinew
ruby jacinth
#

I would just define it in a override file (aka. _custom.yaml), right?

plucky sinew
#

you are right! you know it already 🙂

ruby jacinth
#

one thing I am unclear of, is does it have to be the entire file or can I just have custom.yaml define the ones I want and it will override the others?

#

ie. if node.yaml is the default and I want to include node_custom.yaml instead, do I have to add the entire file or will adding one counter to the custom one override the other?

#

its not clear to me how / when those get overridden

plucky sinew
#

no need to define full template for Zapi collector. It does merge. Example here https://netapp.github.io/harvest/22.11/configure-templates/#how-to-extend-a-zapizapiperf-collectors-existing-object-template
Attached image is fine in your custom template for Zapi collector.
A side note: For Rest collector, we expect to define full template for extending an existing one. Basically an overwrite it will be.
https://netapp.github.io/harvest/22.11/configure-templates/#how-to-extend-a-restrestperfems-collectors-existing-object-template

ruby jacinth
#

ah, I see now, so I have to define the area that I am modifying the same way as in the original, but i don't have to include all the rest of the items

#

I'll give it a try on one of the templates I have modified from the original and see what it does

#

do I need to do a 'include' in the default template file for these _custom.yaml to be included?

#

I'll be trying this out on monday or tuesday next week.