[dev.icinga.com #1058] Optionally allow empty hostgroup assigment for services #167

Closed
icinga-migration opened this Issue Dec 17, 2010 · 1 comment

Projects

None yet

1 participant

@icinga-migration
Member

This issue has been migrated from Redmine: https://dev.icinga.com/issues/1058

Created by mfriedrich on 2010-12-17 16:44:24 +00:00

Assignee: Wolfgang
Status: Resolved (closed on 2011-01-23 11:23:28 +00:00)
Target Version: 1.3
Last Update: 2011-01-23 11:23:28 +00:00 (in Redmine)


# ALLOW EMPTY HOSTGROUP ASSIGMENT FOR SERVICES
# This boolean option determines whether services assigned to empty
# host groups (host groups with no host members) will cause Icinga to
# exit with error on start up (or during a configuration check) or not.
# The default behavior if the option is not present in the main
# configuration file is for Icinga to exit with error if services are
# associated with host groups that have no hosts associated with them.

#allow_empty_hostgroup_assignment=0

+

+
+
+
+
+Allow Empty Hostgroup Assignment
+
+
+
+
+
+
+
+
+
+
+
+Format:
+
+allow_empty_hostgroup_assignment=[01]

+
+
+
+
+Example:

+allow_empty_hostgroup_assignment=1
+
+
+
+
+
+
+
+
+This boolean option determines whether services assigned to empty host groups (host groups with no host members) will cause Nagios to exit with error on start up (or during a configuration check) or not.  The default behavior if the option is not present in the main configuration file is for Nagios to exit with error if services are associated with host groups that have no hosts associated with them.  Enabling this option can be useful when:
+
+
+
+   Configuration files or pre-cached object files are distributed across many Nagios pollers. 
+   Automation is used to generate a Nagios configuration file tree. 
+   There is one set of services maintained by administrators that users may add to their hosts through host group membership for convenience (e.g. a suite of checks associated with a remote monitoring agent) but there is no guarantee that users will use the services associated with the host group (e.g. a remote agent that is being deprecated over time).
+

Relations:

@icinga-migration
Member

Updated by Wolfgang on 2011-01-23 11:23:28 +00:00

  • Status changed from New to Resolved
  • Assigned to set to Wolfgang
  • Done % changed from 0 to 100

pushed to git master (406636d)

@icinga-migration icinga-migration added this to the 1.3 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment