/** * Icinga 2 configuration file * - this is where you define settings for the Icinga application including * which hosts/services to check. * * For an overview of all available configuration options please refer * to the documentation that is distributed as part of Icinga 2. */ /** * The constants.conf defines global constants. */ include "constants.conf" /** * The zones.conf defines zones for a cluster setup. * Not required for single instance setups. */ include "zones.conf" /** * The Icinga Template Library (ITL) provides a number of useful templates * and command definitions. * Common monitoring plugin command definitions are included separately. */ include include include include /** * This includes the Icinga 2 Windows plugins. These command definitions * are required on a master node when a client is used as command endpoint. */ include /** * This includes the NSClient++ check commands. These command definitions * are required on a master node when a client is used as command endpoint. */ include /** * The features-available directory contains a number of configuration * files for features which can be enabled and disabled using the * icinga2 feature enable / icinga2 feature disable CLI commands. * These commands work by creating and removing symbolic links in * the features-enabled directory. */ include "features-enabled/*.conf" /** * Although in theory you could define all your objects in this file * the preferred way is to create separate directories and files in the conf.d * directory. Each of these files must have the file extension ".conf". */ include /** * This includes the Icinga 2 Windows plugins. These command definitions * are required on a master node when a client is used as command endpoint. */ include /** * This includes the NSClient++ check commands. These command definitions * are required on a master node when a client is used as command endpoint. */ include /** * The features-available directory contains a number of configuration * files for features which can be enabled and disabled using the * icinga2 feature enable / icinga2 feature disable CLI commands. * These commands work by creating and removing symbolic links in * the features-enabled directory. */ include "features-enabled/*.conf" /** * Although in theory you could define all your objects in this file * the preferred way is to create separate directories and files in the conf.d * directory. Each of these files must have the file extension ".conf". */ // Disabled by the node setup CLI command on 2021-07-13 09:08:40 +0200 // Disabled by the node setup CLI command on 2021-07-15 11:53:40 +0200 // include_recursive "conf.d" // Added by the node setup CLI command on 2021-07-13 09:08:40 +0200 include "conf.d/api-users.conf"