By default, under path “/var/pnp4nagios/perfdata” the xml file of the check “if64” uses template “check_mk-if64”. For some reason, I created a new template “new_check_mk-if64”.
How can I force current xml files to point to the new template file “new_check_mk-if64”?
Also, I need newly added switch devices to also use the new template“new_check_mk-if64”.
Hi you can’t do that.
All services of same check type use the same template.
If you need to change the template change the “original” template and be sure to have done that when you update you CMK installation.
In OMD env that would be much easier as there’re two folder structures: one for shipped files, one for customized/added files; updates only update shipped files…
By default, under path “/var/pnp4nagios/perfdata” the xml file of the check “if64” uses template “check_mk-if64”. For some reason, I created a new template “new_check_mk-if64”.
How can I force current xml files to point to the new template file “new_check_mk-if64”?
Also, I need newly added switch devices to also use the new template“new_check_mk-if64”.
How does the check“ if64”
know that it should use the template “check_mk-if64” originally?
If I create a new check “new-check”, how can I configure the check to use a template?
Regards,
Denis
···
Hi you can’t do that.
All services of same check type use the same template.
If you need to change the template change the “original” template and be sure to have done that when you update you CMK installation.
In OMD env that would be much easier as there’re two folder structures: one for shipped files, one for customized/added files; updates only update shipped files…
By default, under path “/var/pnp4nagios/perfdata” the xml file of the check “if64” uses template “check_mk-if64”. For some reason, I created a new template “new_check_mk-if64”.
How can I force current xml files to point to the new template file “new_check_mk-if64”?
Also, I need newly added switch devices to also use the new template“new_check_mk-if64”.
All services of same check type use the same template.
If you need to change the template change the “original” template and be sure to have done that when you update you CMK installation.
In OMD env that would be much easier as there’re two folder structures: one for shipped files, one for customized/added files; updates only update shipped files…
By default, under path “/var/pnp4nagios/perfdata” the xml file of the check “if64” uses template “check_mk-if64”. For some reason, I created a new template “new_check_mk-if64”.
How can I force current xml files to point to the new template file “new_check_mk-if64”?
Also, I need newly added switch devices to also use the new template“new_check_mk-if64”.
All services of same check type use the same template.
If you need to change the template change the “original” template and be sure to have done that when you update you CMK installation.
In OMD env that would be much easier as there’re two folder structures: one for shipped files, one for customized/added files; updates only update shipped files…
By default, under path “/var/pnp4nagios/perfdata” the xml file of the check “if64” uses template “check_mk-if64”. For some reason, I created a new template “new_check_mk-if64”.
How can I force current xml files to point to the new template file “new_check_mk-if64”?
Also, I need newly added switch devices to also use the new template“new_check_mk-if64”.