Using multiple nrds config files for a single host

[skynardo]

I have rolled out a NRDS standard checks config file to all of our AIX lpars to monitor cpu, swap, filesystems etc. Now I'd like to roll out additional checks on specific lpars (i.e. db2 checks for servers that are running db2), but would like to use my AIX_standard_checks config file and add a AIX_db2_checks config file . I was hoping there was a way to do this via NRDS Config Mgr so we could take advantage of central config file management without duplicating my standard checks configurations for every host that requires additional checks. I've done some looking around and found old posts (2013 or earlier) that say this is not possible. I was just wanting to verify this is the case before moving forward. Are there any plans to allow for multiple config names in the future?

[lmiltchev]

Your title is "Using multiple nrds config files for a single host", however you are saying: "...so we could take advantage of central config file management without duplicating my standard checks configurations for every host that requires additional checks." Can you explain? Are we talking about multiple configs for a single host or same config for multiple hosts that needs to be "tweaked" for some of the hosts?

You can edit a config from within the NRDS Config Manager (add/delete/modify commands, etc.). The changes will be pushed next time the cron job is run on the client machine, and the config verson number will be incremented.

If you need to add "custom" commands to each host, you will need to have separate configs (for each host) in the NRDS Config Manager.

[skynardo]

Today it looks like the NRDS Config file points to the CONFIG_NAME residing on the XI server which consists of a single set of checks. I was thinking If this CONFIG_NAME could represent a group of servers (TOMCAT or LINUX for example) and contain pointers to other config files that have the actual checks (i.e. standard_linux_checks, tomcat_checks, postgres_checks), then we could manage each of those config files for our standard checks for each type(group) of hosts. If down the road we want to add a check to ALL linux servers, we would modify the standard_linux_checks config on the XI server, and any CONFIG_NAME that contains the standard_linux_checks pointer would get pushed out. I assume this approach would either need to merge the actual config files at one end or the other.

[Box293]

So I had a customer doing something similar recently. This may not be exactly what you want, but this information will be useful.

His goal was that he had some checks he only wanted to run once a day, so he created a separate cron job that pointed to a separate config file.

For example:

Code: Select all

/usr/local/nrdp/clients/nrds/nrds.pl -H a_host_name -c /usr/local/nrdp/clients/nrds/nrds2.cfg

This does work, however there is a bug that needs fixing. I've reported it here:
http://tracker.nagios.com/view.php?id=695

Basically you just need to update nrds.pl to send the -c argument and value to nrds_updater.pl, it all works as expected.

[skynardo]

OK, this might be something I could use. To be clear, I need to modify nrds.pl so that if -c /path/to/nrds.cfg is passed, it will pass "-c /path/to/nrds.cfg" to /usr/local/nrdp/clients/nrds/nrds_updater.pl?
I tried looking at the bug report but I'm not authorized. Can you tell me what that issue is so I can decide if I want to test this out?

Thanks

[Box293]

OK, this might be something I could use. To be clear, I need to modify nrds.pl so that if -c /path/to/nrds.cfg is passed, it will pass "-c /path/to/nrds.cfg" to /usr/local/nrdp/clients/nrds/nrds_updater.pl?

Yes that is correct, nrds_updater.pl is simply not being passed the -c argument.

I tried looking at the bug report but I'm not authorized.

You can signup for an account, anyone is allowed

http://tracker.nagios.com/signup_page.php