<emclass="default">(defaults to: <tt>'nagios.example.net'</tt>)</em>
—
<divclass='inline'>
<p>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.</p>
</div>
</li>
<li>
<spanclass='name'>ng_reqpackages_server</span>
<spanclass='type'>(<tt>Array</tt>)</span>
<emclass="default">(defaults to: <tt>['nagios','nagios-devel']</tt>)</em>
—
<divclass='inline'>
<p>An array of packages to be installed on the Nagios server.</p>
</div>
</li>
<li>
<spanclass='name'>ng_reqpackages_client</span>
<spanclass='type'>(<tt>Array</tt>)</span>
<emclass="default">(defaults to: <tt>['net-snmp-utils','nagios-plugins','nagios-plugins-all','nagios-plugins-nrpe','nagios-common']</tt>)</em>
—
<divclass='inline'>
<p>An array of packages to be installed on the Nagios clients.</p>
</div>
</li>
<li>
<spanclass='name'>ng_pkg_ensure</span>
<spanclass='type'>(<tt>String</tt>)</span>
<emclass="default">(defaults to: <tt>'present'</tt>)</em>
—
<divclass='inline'>
<p>The ensure value for all packages. Default is ‘present’.</p>
</div>
</li>
<li>
<spanclass='name'>ng_user</span>
<spanclass='type'>(<tt>String</tt>)</span>
<emclass="default">(defaults to: <tt>'nagios'</tt>)</em>
—
<divclass='inline'>
<p>The name of the Nagios user to be created on the Nagios server. Default is ‘nagios’.</p>
</div>
</li>
<li>
<spanclass='name'>ng_u_comment</span>
<spanclass='type'>(<tt>String</tt>)</span>
<emclass="default">(defaults to: <tt>'Nagios User'</tt>)</em>
—
<divclass='inline'>
<p>The comment field for the Nagios user. Default is ‘Nagios User’.</p>
</div>
</li>
<li>
<spanclass='name'>ng_u_groups</span>
<spanclass='type'>(<tt>String</tt>)</span>
<emclass="default">(defaults to: <tt>'nagios'</tt>)</em>
—
<divclass='inline'>
<p>The group(s) to which the Nagios user should be added. Default is ‘nagios’.</p>
</div>
</li>
<li>
<spanclass='name'>ng_u_shell</span>
<spanclass='type'>(<tt>String</tt>)</span>
<emclass="default">(defaults to: <tt>'/sbin/nologin'</tt>)</em>
—
<divclass='inline'>
<p>The login shell for the Nagios user. Default is ‘/sbin/nologin’.</p>
</div>
</li>
<li>
<spanclass='name'>ng_u_home</span>
<spanclass='type'>(<tt>String</tt>)</span>
<emclass="default">(defaults to: <tt>'/home/nagios'</tt>)</em>
—
<divclass='inline'>
<p>The home directory for the Nagios user. Default is ‘/home/nagios’.</p>
</div>
</li>
<li>
<spanclass='name'>ng_u_uid</span>
<spanclass='type'>(<tt>Integer</tt>)</span>
<emclass="default">(defaults to: <tt>1004</tt>)</em>
—
<divclass='inline'>
<p>The user ID for the Nagios user. Default is 1004.</p>
</div>
</li>
<li>
<spanclass='name'>ng_include_nrpe</span>
<spanclass='type'>(<tt>Boolean</tt>)</span>
<emclass="default">(defaults to: <tt>true</tt>)</em>
—
<divclass='inline'>
<p>Whether to include the NRPE client on the Nagios clients. Default is true.</p>
<emclass="default">(defaults to: <tt>false</tt>)</em>
—
<divclass='inline'>
<p>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.</p>
<emclass="default">(defaults to: <tt>''</tt>)</em>
—
<divclass='inline'>
<p>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.</p>
<emclass="default">(defaults to: <tt>''</tt>)</em>
—
<divclass='inline'>
<p>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.</p>
<emclass="default">(defaults to: <tt>''</tt>)</em>
—
<divclass='inline'>
<p>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.</p>