New checks and possible zone configuration problem

I haven’t touched this file.

This is on the master:

/**
 * 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 <itl>
include <plugins>
include <plugins-contrib>
include <manubulon>

/**
 * 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 <windows-plugins>

/**
 * This includes the NSClient++ check commands. These command definitions
 * are required on a master node when a client is used as command endpoint.
 */
include <nscp>

/**
 * 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 2019-12-06 13:11:59 +0100
// include_recursive "conf.d"
// Added by the node setup CLI command on 2019-12-06 13:11:59 +0100
#include "conf.d/api-users.conf"

include_recursive "/etc/icinga2/conf.d/"

On the satellite it’s the same but the last line it’s just include_recursive "conf.d"

After running the node wizard…

This line shall be not commented out.

But this one.

Oh I didn’t noticed that include "conf.d/api-users.conf"was commented…
As for conf.d, the node wizard asks if one wants to include it or not and we decided to include it. Should we leave it out?

In a clustered setup? What for?

Actually I don’t know the reasons, but I know that we are still understanding how icinga works so we are open to changes.
So we should not include conf.d and have all our configurations regarding hosts, services and checks inside zones.d, right?

1 Like

It works!

Thank you @Al2Klimov so much!