Nagios Support Forum

Hi Nagios xi,

I'm a long term user of Nagios and have built many (!) highly custom configs. For my current employer, I'm looking at moving from a stable Nagios Core to Nagios xi because of the cleaner UI (for management) and $2500 ish is peanuts to us so it's nice to support Nagios.

I like the concept of Wizard and the "New Solaris Server". However, the way we did the our Nagios Core deployment was via Hostgroups and assigning Service checks to the hostgroups. A new host simply consist of 4 lines that says "host is named thing is belongs to the hostgroup of SOLARIS_SERVERS". However this same concept doesn't appear possible with Nagios xi because Nagios xi wants to use Template to declare new Hosts, but it manually create and assigns the services to that not (ie. it doesn't use hostgroups as a template).

Our config allows us to "assign new Service check to SOLARIS_SERVERS" and immediately we know this will be replicated to all Solaris Servers which belong to it. My first question is, how does Nagios xi resolve this?

My other question is, how do I modify the default Services that get assigned when you instantiate a new {Windows|Linux|Solaris] server? Our client config is super solid (and doesn't accept command args!), so ideally I just want to redefine the default template that's used so when a user instantiates a new Server it's automagically takes on the Services that match our Client nrpe.cfg.

Thanks!

With your particular situation, your best solution might actually be to manually maintain your configs through the /usr/local/nagios/etc/static directory. Everything under this directory is left alone from the Core Config Manager.

All of the templates used by the wizards are prepended with xiwizard_<templatename>. So you can change the default templates if that works for you.

You'll have to experiment and see what option works best for you, but I do know there are some users who bypass the wizards and the Core Config Manager altogether because they have reliable systems in place to manually maintain their configs.