Nagios Support Forum

I'd like to setup a QA and production nagios XI instance where the QA and production instances have the same service checks and all service checks have only hostgroups as members. This way I can test configurations with one host and promote the service check from QA to production and run with another set of hosts. Since we'll have many more hosts in production than QA, will I run into a problem, if I end up with a hostgroup in QA that has no members (assigned to a service check).

Thanks!

You shouldn't have a problem adding a service to a hostgroup, if that's what you asking. Let me know if I misunderstood your question.

It's possible that my QA environment could have a hostgroup that once held a member that has been promoted to production and no longer exists in QA. I'd like to be able to create a service definition in my QA environment which references not hostnames and only hostgroups. If there are hosts in the hostgroups, I don't have a problem. If there are no hosts currently in the QA hostgroup, then I have a problem. How can I have Nagios accept a hostgroup with no members or do I have to add "dummy" host to all hostgroups?

I see that in with Nagios XI CCM configuration that I can click on "null" as a hostgroup option. What does this do for me? I'd like to keep the service group and hostgroup association alive between QA when promoting the service from QA to production....

My apologizes if I'm not clear. Thanks!

I can configure a "dummy" host in maintenance mode and add that to every hostgroup and that gets around the nagios empty hostgroup verification, however, that leaves me with a different, though less annoying problem. I know have services on the dummy host in a failed state. How can I reset their value to green? If I can do this, then my problem is sufficiently solved.

Thanks for your patience.

Submit a passive check of "ok" or "up". They will remain in an ok state if they are not checked again.

This solves my problem. Thanks for your help!