confdroid_nagios::params Module name: confdroid_nagios Author: 12ww1160 (12ww1160@confdroid.com)
-The hostname or IP address of the Nagios server. This will determine the installation selection and the of the clients to connect to the Nagios server.
-An array of packages to be installed on the Nagios server.
-An array of packages to be installed on the Nagios clients.
-The ensure value for all packages. Default is ‘present’.
-The name of the Nagios user to be created on the Nagios server. Default is ‘nagios’.
-The comment field for the Nagios user. Default is ‘Nagios User’.
-The group(s) to which the Nagios user should be added. Default is ‘nagios’.
-The login shell for the Nagios user. Default is ‘/sbin/nologin’.
-The home directory for the Nagios user. Default is ‘/home/nagios’.
-The user ID for the Nagios user. Default is 1004.
-Whether to include the NRPE client on the Nagios clients. Default is true.
-Whether to configure the Nagios web interface to use HTTPS. Default is false. We recommend using a reverse proxy with SSL termination in front of the Nagios web interface, so this is disabled by default.
-The event broker module to be used in the Nagios configuration. Default is an empty string, which means no event broker module will be configured. You can specify a module like ‘mod_gearman’ to enable the Gearman event broker module, for example.
-The global host event handler to be used in the Nagios configuration. Default is an empty string, which means no global host event handler will be configured. You can specify a command like ‘notify-host-by-email’ to set a global host event handler that sends email notifications for host events, for example.
-The global service event handler to be used in the Nagios configuration. Default is an empty string, which means no global service event handler will be configured. You can specify a command like ‘notify-service-by-email’ to set a global service event handler that sends email notifications for service events, for example.
-The number of check worker processes to be configured in the Nagios configuration. Default is an empty string, which means no specific number of check worker processes will be configured. You can specify a number like ‘5’ to set the number of check worker processes to 5, for example.
-The path to the Nagios log file. Default is ‘/var/log/nagios/nagios.log’.
-The path to the Nagios object cache file. Default is ‘/var/spool/nagios/objects.cache’.
-The path to the Nagios precached object file. Default is ‘/var/spool/nagios/objects.precache’.
-The path to the Nagios resource file. Default is ‘/etc/nagios/private/resource.cfg’.
-The path to the Nagios status file. Default is ‘/var/log/nagios/status.dat’.
-The interval for updating the Nagios status file. Default is ‘10’.
-Whether to enable external command checking in the Nagios configuration. Default is ‘1’, which means external command checking will be enabled. You can set this to ‘0’ to disable external command checking if needed.
-The path to the Nagios command file. Default is ‘/var/spool/nagios/cmd/nagios.cmd’.
-The path to the Nagios lock file. Default is ‘/var/run/nagios/nagios.pid’.
-The path to the Nagios temporary file. Default is ‘/var/spool/nagios/nagios.tmp’.
-The path to the Nagios temporary directory. Default is ‘/tmp’.
-The options for the Nagios event broker. Default is ‘-1’, which means no specific options will be configured. You can specify options like ‘–log-level=debug’ to set the log level for the event broker, for example.
-The method for log rotation in the Nagios configuration. Default is ‘h’, which means hourly log rotation. You can set this to ‘d’ for daily log rotation, ‘w’ for weekly log rotation, or ‘m’ for monthly log rotation if needed.
-The path to the Nagios log archive directory. Default is ‘/var/log/nagios/archives’.
-Whether to use syslog for logging in the Nagios configuration. Default is ‘1’, which means syslog will be used for logging. You can set this to ‘0’ to disable syslog logging if needed.
-Whether to log notifications in the Nagios configuration. Default is ‘1’, which means notifications will be logged. You can set this to ‘0’ to disable logging of notifications if needed.
-Whether to log service retries in the Nagios configuration. Default is ‘1’, which means service retries will be logged. You can set this to ‘0’ to disable logging of service retries if needed.
-Whether to log host retries in the Nagios configuration. Default is ‘1’, which means host retries will be logged. You can set this to ‘0’ to disable logging of host retries if needed.
-Whether to log event handlers in the Nagios configuration. Default is ‘1’, which means event handlers will be logged. You can set this to ‘0’ to disable logging of event handlers if needed.
-Whether to log initial states in the Nagios configuration. Default is ‘0’, which means initial states will not logged. You can set this to ‘1’ to enable logging of initial states if needed.
-Whether to log current states in the Nagios configuration. Default is ‘1’, which means current states will be logged. You can set this to ‘0’ to disable logging of current states if needed.
-Whether to log external commands in the Nagios configuration. Default is ‘1’, which means external commands will be logged. You can set this to ‘0’ to disable logging of external commands if needed.
-Whether to log passive checks in the Nagios configuration. Default is ‘1’, which means passive checks will be logged. You can set this to ‘0’ to disable logging of passive checks if needed.
-The interval for delaying service checks in the Nagios configuration. Default is ‘s’, which means service checks will be delayed until the next scheduled check interval. You can set this to a specific number of seconds (e.g., ‘30’) to delay service checks by that amount of time if needed.
-The maximum spread for service checks in the Nagios configuration. Default is ‘30’, which means service checks will be spread out over a maximum of 30 seconds. You can set this to a different number of seconds if needed to control how service checks are distributed over time.
-The interleave factor for service checks in the Nagios configuration. Default is ‘s’, which means service checks will be interleaved based on their scheduled check intervals. You can set this to a specific number (e.g., ‘0.5’) to control the degree of interleaving for service checks if needed.
-The interval for delaying host checks in the Nagios configuration. Default is ‘s’, which means host checks will be delayed until the next scheduled check interval. You can set this to a specific number of seconds (e.g., ‘30’) to delay host checks by that amount of time if needed.
-The maximum spread for host checks in the Nagios configuration. Default is ‘30’, which means host checks will be spread out over a maximum of 30 seconds. You can set this to a different number of seconds if needed to control how host checks are distributed over time.
-The maximum number of concurrent checks in the Nagios configuration. Default is ‘0’, which means there is no limit in the Nagios configuration. This means that Nagios will allow as many concurrent checks as the system can handle. You can set this to a specific number (e.g., ‘10’) to limit the number of concurrent checks if needed to prevent resource exhaustion.
-The frequency for the check result reaper in the Nagios configuration. Default is ‘10’, which means the check result reaper will run every 10 seconds. You can set this to a different number of seconds if needed to control how often the check result reaper runs.
-The maximum time for check result reaping in the Nagios configuration. Default is ‘30’, which means check results will be reaped if they are older than 30 seconds. You can set this to a different number of seconds if needed to control how long check results are kept before being reaped.
-The path to the Nagios check result directory. Default is ‘/var/spool/nagios/checkresults’.
-The maximum age for check result files in the Nagios configuration. Default is ‘3600’, which means check result files will be considered stale and reaped if they are older than 3600 seconds (1 hour). You can set this to a different number of seconds if needed to control how long check result files are kept before being considered stale.
-The cached host check horizon in the Nagios configuration. Default is ‘15’, which means host check results will be cached for 15 seconds. You can set this to a different number of seconds if needed to control how long host check results are cached.
-The cached service check horizon in the Nagios configuration. Default is ‘15’, which means service check results will be cached for 15 seconds. You can set this to a different number of seconds if needed to control how long service check results are cached.
-Whether to perform predictive host dependency checks in the Nagios configuration. Default is ‘1’, which means predictive host dependency checks will be performed. You can set this to ‘0’ to disable predictive host dependency checks. Predictive host dependency checks can help reduce false positives by checking the status of parent hosts before determining the status of child hosts.
-Whether to perform predictive service dependency checks in the Nagios configuration. Default is ‘1’, which means predictive service dependency checks will be performed. You can set this to ‘0’ to disable predictive service dependency checks. Predictive service dependency checks can help reduce false positives by checking the status of parent services before determining the status of child services.
-Whether to use soft state dependencies in the Nagios configuration. Default is ‘0’, which means soft state dependencies will not be used. You can set this to ‘1’ to enable soft state dependencies if needed. Soft state dependencies allow Nagios to delay the propagation of host and service states based on the number of check attempts and the state of the checks, which can help reduce false positives during transient issues.
-The time change threshold in the Nagios configuration. Default is ‘900’, which means a time change of 900 seconds (15 minutes) or more will be considered significant and may trigger certain actions in Nagios. You can set this to a different number of seconds if needed to control how Nagios responds to significant time changes.
-Whether to automatically reschedule checks in the Nagios configuration. Default is ‘0’, which means checks will not be automatically rescheduled. You can set this to ‘1’ to enable automatic rescheduling of checks if needed. Automatic rescheduling can help ensure that checks are performed in a timely manner, especially after significant time changes or when the Nagios daemon is restarted.
-The interval for automatically rescheduling checks in the Nagios configuration. Default is ‘30’, which means checks will be automatically rescheduled every 30 seconds if automatic rescheduling is enabled. You can set this to a different number of seconds if needed to control how often checks are automatically rescheduled.
-The window for automatically rescheduling checks in the Nagios configuration. Default is ‘180’, which means checks will be automatically rescheduled if they are within 180 seconds (3 minutes) of their scheduled check time when automatic rescheduling is enabled. You can set this to a different number of seconds if needed to control the window for automatic rescheduling of checks.
-The timeout for service checks in the Nagios configuration. Default is ‘60’, which means service checks will time out after 60 seconds. You can set this to a different number of seconds if needed to control how long Nagios will wait for a service check to complete before timing out.
-The timeout for host checks in the Nagios configuration. Default is ‘30’, which means host checks will time out after 30 seconds. You can set this to a different number of seconds if needed to control how long Nagios will wait for a host check to complete before timing out.
-The timeout for event handlers in the Nagios configuration. Default is ‘30’, which means event handlers will time out after 30 seconds. You can set this to a different number of seconds if needed to control how long Nagios will wait for an event handler to complete before timing out.
-The timeout for notifications in the Nagios configuration. Default is ‘30’, which means notifications will time out after 30 seconds. You can set this to a different number of seconds if needed to control how long Nagios will wait for a notification to be sent before timing out.
-The timeout for obsess over service checks in the Nagios configuration. Default is ‘5’, which means obsess over service checks will time out after 5 seconds. You can set this to a different number of seconds if needed to control how long Nagios will wait for an obsess over service check to complete before timing out.
-The timeout for processing performance data in the Nagios configuration. Default is ‘5’, which means processing of performance data will time out after 5 seconds. You can set this to a different number of seconds if needed to # control how long Nagios will wait for performance data processing to complete before timing out.
-Whether to retain state information in the Nagios configuration. Default is ‘1’, which means state information will be retained. You can set this to ‘0’ to disable retention of state information if needed. Retaining state information allows Nagios to keep track of the current status of hosts and services, which can be useful for reporting and for making informed decisions about notifications and event handling.
-The path to the Nagios state retention file. Default is ‘/var/spool/nagios/retention.dat’.
-The interval for updating the state retention file in the Nagios configuration. Default is ‘60’, which means the state retention file will be updated every 60 seconds. You can set this to a different number of seconds if needed to control how often the state retention file is updated.
-Whether to use the retention program state in the Nagios configuration. Default is ‘1’, which means the retention program state will be used. You can set this to ‘0’ to disable the use of the retention program state if needed. The retention program state allows Nagios to retain the state of the Nagios daemon itself, which can be useful for determining if the daemon was restarted and for controlling how checks and notifications are handled after a restart.
-Whether to use the retention scheduling information in the Nagios configuration. Default is ‘1’, which means the retention scheduling information will be used. You can set this to ‘0’ to disable the use of the retention scheduling information if needed. The retention scheduling information allows Nagios to retain information about the scheduled check times for hosts and services, which can help ensure that checks are performed at the correct times even after a restart.
-The retention host attribute mask in the Nagios configuration. Default is ‘0’, which means no specific host attributes will be retained. You can set this to a specific value (e.g., ‘1’) to control which host attributes are retained in the state retention file if needed.
-The retention service attribute mask in the Nagios configuration. Default is ‘0’, which means no specific service attributes will be retained. You can set this to a specific value (e.g., ‘1’) to control which service attributes are retained in the state retention file if needed.
-The retention processed host attribute mask in the Nagios configuration. Default is ‘0’, which means no specific processed host attributes will be retained. You can set this to a specific value (e.g., ‘1’) to control which processed host attributes are retained in the state retention file if needed.
-The retention processed service attribute mask in the Nagios configuration. Default is ‘0’, which means no specific processed service attributes will be retained. You can set this to a specific value (e.g., ‘1’) to control which processed service attributes are retained in the state retention file if needed.
-The retention contact host attribute mask in the Nagios configuration. Default is ‘0’, which means no specific contact host attributes will be retained. You can set this to a specific value (e.g., ‘1’) to control which contact host attributes are retained in the state retention file if needed.
-The retention contact service attribute mask in the Nagios configuration. Default is ‘0’, which means no specific contact service attributes will be retained. You can set this to a specific value (e.g., ‘1’) to control which contact service attributes are retained in the state retention file if needed.
-The length of the time intervals in the Nagios configuration. Default is ‘60’, which means time intervals will be 60 seconds long. You can set this to a different number of seconds if needed to control the length of time intervals for scheduling checks and other time-based actions in Nagios.
-Whether to check for updates in the Nagios configuration. Default is ‘1’, which means Nagios will check for updates to the Nagios configuration files. You can set this to ‘0’ to disable checking for updates if needed. Checking for updates allows Nagios to detect changes to the configuration files and reload the configuration as needed to apply those changes.
-Whether to perform a bare update check in the Nagios configuration. Default is ‘0’, which means a bare update check will not be performed. You can set this to ‘1’ to enable bare update checks if needed. A bare update check allows Nagios to check for updates to the configuration files without performing a full check of the configuration, which can be useful in certain scenarios.
-Whether to use aggregate host checking in the Nagios configuration. Default is ‘0’, which means aggregate host checking will not be used. You can set this to ‘1’ to enable aggregate host checking if needed. Aggregate host checking allows Nagios to perform checks on groups of hosts and determine the status of the group based on the status of the individual hosts, which can be useful for monitoring clusters or other groups of related hosts.
-Whether to execute service checks in the Nagios configuration. Default is ‘1’, which means service checks will be executed. You can set this to ‘0’ to disable execution of service checks if needed.
-Whether to execute host checks in the Nagios configuration. Default is ‘1’, which means host checks will be executed. You can set this to ‘0’ to disable execution of host checks if needed.
-Whether to accept passive service checks in the Nagios configuration. Default is ‘1’, which means passive service checks will be accepted. You can set this to ‘0’ to disable acceptance of passive service checks if needed.
-Whether to accept passive host checks in the Nagios configuration. Default is ‘1’, which means passive host checks will be accepted. You can set this to ‘0’ to disable acceptance of passive host checks if needed.
-Whether to enable notifications in the Nagios configuration. Default is ‘1’, which means notifications will be enabled. You can set this to ‘0’ to disable notifications if needed.
-Whether to enable event handlers in the Nagios configuration. Default is ‘1’, which means event handlers will be enabled. You can set this to ‘0’ to disable event handlers if needed.
-Whether to process performance data in the Nagios configuration. Default is ‘1’, which means performance data will be processed. You can set this to ‘0’ to disable processing of performance data if needed.
-The command to process host performance data in the Nagios configuration. Default is ”, which means no specific command will be configured for processing host performance data. You can set this to a specific command if needed.
-The command to process service performance data in the Nagios configuration. Default is ”, which means no specific command will be configured for processing service performance data. You can set this to a specific command if needed.
-The file to which host performance data will be written in the Nagios configuration. Default is ”, which means no specific file will be configured for host performance data. You can set this to a specific file path if needed.
-The file to which service performance data will be written in the Nagios configuration. Default is ”, which means no specific file will be configured for service performance data. You can set this to a specific file path if needed.
-The template for host performance data in the Nagios configuration. Default is ”, which means no specific template will be configured for host performance data. You can set this to a specific template if needed.
-The template for service performance data in the Nagios configuration. Default is ”, which means no specific template will be configured for service performance data. You can set this to a specific template if needed.
-The file mode for host performance data files in the Nagios configuration.
-The file mode for service performance data files in the Nagios configuration.
-The interval for processing host performance data in the Nagios configuration. Default is ‘0’, which means host performance data will be processed immediately. You can set this to a specific number of seconds if needed to control how often host performance data is processed.
-The interval for processing service performance data in the Nagios configuration. Default is ‘0’, which means service performance data will be processed immediately. You can set this to a specific number of seconds if needed to control how often service performance data is processed.
-The command to process service performance data in the Nagios configuration.
-The command to process host performance data in the Nagios configuration.
-Whether to obsess over services in the Nagios configuration. Default is ‘0’, which means not to obsess over services. You can set this to ‘1’ to enable obsessing over services if needed.
-The command to process obsessive service checks in the Nagios configuration. Default is ”, which means no specific command will be configured for obsessive service checks. You can set this to a specific command if needed.
-Whether to obsess over hosts in the Nagios configuration. Default is ‘0’, which means not to obsess over hosts. You can set this to ‘1’ to enable obsessing over hosts if needed.
-The command to process obsessive host checks in the Nagios configuration. Default is ”, which means no specific command will be configured for obsessive host checks. You can set this to a specific command if needed.
-The expected result for host performance data processing in the Nagios configuration.
-The expected result for service performance data processing in the Nagios configuration.
--418 -419 -420 -421 -422 -423 -424 -425 -426 -427 428 429 430 @@ -2765,10 +2229,18 @@ inherited by all classes except defines. 664 665 666 -667+667 +668 +669 +670 +671 +672 +673 +674 +675
# File 'manifests/params.pp', line 418
+ # File 'manifests/params.pp', line 428
class confdroid_nagios::params (
@@ -2921,8 +2393,6 @@ class confdroid_nagios::params (
String $ng_mail_user = 'admin@example.net',
String $ng_page_user = 'pageadmin@example.net',
-
-
# httpd
Boolean $ng_use_https = false,