Forge Home


Fork of puppet-icingaweb2 (65311a9) solving stdlib dependencies


7,189 latest version

4.3 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 1.0.6 (deleted)
  • 0.0.1 (latest)
released Mar 13th 2017
This version is compatible with:
  • Puppet Enterprise 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 3.8.0 < 5.0.0

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'factorit-icingaweb2', '0.0.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add factorit-icingaweb2
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install factorit-icingaweb2 --version 0.0.1

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



factorit/icingaweb2 — version 0.0.1 Mar 13th 2017

Icinga Web 2

Puppet Forge Build Status Github Tag Puppet Forge Downloads

Table of Contents

  1. Description
  2. Setup - The basics of getting started with Icinga Web 2
  3. Usage - Configuration options and additional functionality
  4. Reference - An under-the-hood peek at what the module is doing and how
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module


This module installs and configures Icinga Web 2.

Icinga Web 2 is the next generation open source monitoring web interface, framework and command-line interface developed by the Icinga Project, supporting Icinga 2, Icinga Core and any other monitoring backend compatible with the Livestatus Protocol.


Setup requirements

Beginning with Icinga Web 2

node /box/ {
  include icingaweb2


Install method: packages

node /box/ {
  class { 'icingaweb2':
    install_method => 'package',

Install method: Git

node /box/ {
  class { 'icingaweb2':
    install_method => 'git',

Initialize db

Default Credentials will be icingaadmin:icinga

node /box/ {
  class { 'icingaweb2':
    initialize => true,

Manage repository

Note: This will add the same repositories as icinga/icinga2, make sure you only enable one.

class { '::icingaweb2':
  manage_repo    => true,
  install_method => 'package',

Monitoring module

In minimal default configuration:

include ::icingaweb2
include ::icingaweb2::mod::monitoring

With transport configuration

include ::icingaweb2

# default is local
class { '::icingaweb2::mod::monitoring':
  transport      => 'local',
  transport_path => '/run/icinga2/cmd/icinga2.cmd',

# via SSH, make sure to add a SSH key to the user running PHP (apache)
class { '::icingaweb2::mod::monitoring':
  transport          => 'remote',
  transport_host     => 'icinga-master1',
  transport_username => 'icingaweb',
  transport_path     => '/run/icinga2/cmd/icinga2.cmd',

# via Icinga 2 API
class { '::icingaweb2::mod::monitoring':
  transport          => 'api',
  transport_host     => 'icinga-master1',
  transport_username => 'icingaweb2',
  transport_password => 'secret',

Business process module

node /box/ {
  class {

Deployment module

node /box/ {
  class {
      auth_token => 'secret_token';

Graphite module

node /box/ {
  class {
      graphite_base_url => '';

NagVis module

node /box/ {
  class {
      nagvis_url => '';

Real world example

Icinga2 is installed or on another host. One needs only the ido data to configure icingaweb2. This could be a profile class to include icingaweb2 in a architecture with roles and profiles.

class profile::icingaweb2(){
  $ido_db_name = hiera('icinga2::ido::name', 'icinga2')
  $ido_db_user = hiera('icinga2::ido::user', 'icinga2')
  $ido_db_pass = hiera('icinga2::ido::password', 'icinga2')
  $web_db_name = hiera('icingaweb2::db::name', 'icingaweb2')
  $web_db_user = hiera('icingaweb2::db::user', 'icingaweb2')
  $web_db_pass = hiera('icingaweb2::db::password', 'icingaweb2')

  contain '::mysql::server'
  contain '::mysql::client'
  contain '::mysql::server::account_security'

  contain '::apache'
  contain '::apache::mod::php'

  Exec { path => [ '/bin/', '/sbin/' , '/usr/bin/', '/usr/sbin/' ] }

  ::mysql::db { $web_db_name:
    user     => $web_db_user,
    password => $web_db_pass,
    host     => 'localhost',
    grant    => ['ALL'],

  class { '::icingaweb2':
    initialize          => true,
    install_method      => 'package',
    manage_apache_vhost => true,
    ido_db_name         => $ido_db_name,
    ido_db_pass         => $ido_db_pass,
    ido_db_user         => $ido_db_user,
    web_db_name         => $web_db_name,
    web_db_pass         => $web_db_pass,
    web_db_user         => $web_db_user,
    require             => Class['::mysql::server'],
  } ->

  augeas { 'php.ini':
    context => '/files/etc/php.ini/PHP',
    changes => ['set date.timezone Europe/Berlin',],

  contain ::icingaweb2::mod::monitoring




  • Fork it
  • Create a feature branch (git checkout -b my-new-feature)
  • Run rspec tests (bundle exec rake spec)
  • Commit your changes (git commit -am 'Added some feature')
  • Push to the branch (git push origin my-new-feature)
  • Create new Pull Request