I have updated harvest.yml but haven't extended any of the templates. I briefly looked at it but the process looks rather cumbersome and appears to be release specific. There would ideally be a place that I can put this setting to be in affect for all releases going forward. Without it, I envision a time after I'm gone when an admin goes "we updated to 9.15 and my dashboards are now empty!" conf/rest has directories from 9.6.0 to 9.12.0 and conf/restperf has 9.12.0 to 9.14.1".
'Instead of editing one of the existing templates, it's better to copy one and edit the copy. That way, your custom template wil
l not be overwritten when upgrading Harvest. For example, if you want to change conf/rest/cdot/9.12.0/aggr.yaml, first create
a copy (e.g., conf/rest/cdot/9.12.0/custom_aggr.yaml), then add these lines to conf/rest/custom.yaml:"
not quite what I think I want (but I could be wrong). This is where I know I'll get burned:
"After restarting pollers, aggr.yaml will be ignored and the new, custom_aggr.yaml subtemplate will be used instead."
So when aggr.yaml changes going forward, I'll have to redo the customization.
My thoughts:
At the tail end of the current yaml files, add an "include: custom_FOO.yaml" in a non release-specific directory that lets users override the defaults. Include empty custom_FOO.yaml files so the search will pass and users will know where the file needs to be.