Hi,
I was wondering if there is an easy way to use multiple NRDS configs for a single host and/or use the same config for multiple hosts.
For example I have 3 windows serves. 2 Domain controllers and 1 exchange.
I would like to setup a :
Windows config containing CPU/MEM/DISK tests for all 3 servers
Domaincontroller config containing a DCDIAG test + DC services to the 2 domain controllers
Exchange config containing specific exchange tests to the exchange server
I would also like to do the same thing for linux servers :
Linux config with CPU/MEM/DISK
MySQL config
...
Is this possible with NRDS ?
I have read the following posts but I don't think it's is a good idea to have to manually change crontabs/scheduled tasks on the client side
https://support.nagios.com/forum/viewto ... 5&p=132184
http://serverfault.com/questions/517088 ... figuration
Wouldn't it be easier if the crontab/scheduled tasks had the name of the config io the name of the hostname ?
Using multiple nrds config files for a single host
- Nagios Support
- Posts: 36
- Joined: Thu Sep 04, 2014 12:16 pm
Re: Using multiple nrds config files for a single host
It doesn't seem that it is possible. We will need to do some digging into this, and will get back to you within the next 24 hours.Is this possible with NRDS ?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Using multiple nrds config files for a single host
Having multiple configs per single host isn't possible. When the installer runs, it creates the same config files so the previous install will be over written.
However, we did some checking and you can use a single config for multiple hosts. At install time, if you use localhost as the hostname, the NRDS client will look up the hostname and substitute that for the config name.
However, we did some checking and you can use a single config for multiple hosts. At install time, if you use localhost as the hostname, the NRDS client will look up the hostname and substitute that for the config name.
Be sure to check out our Knowledgebase for helpful articles and solutions!