monit

pdk
deprecated
Puppet module for Monit

Example42

example42

17,791 downloads

3,137 latest version

4.8 quality score

Version information

  • 2.1.1 (latest)
  • 2.0.18
  • 2.0.17
  • 2.0.16
  • 2.0.15
  • 2.0.14
  • 2.0.13
  • 2.0.12
  • 2.0.11
released Apr 19th 2019
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2016.4.x
  • Puppet >= 4.10.0 < 7.0.0
  • CentOS
    ,
    OracleLinux
    ,
    RedHat
    ,
    Scientific
    ,
    Debian
    ,
    Ubuntu
This module has been deprecated by its author since Oct 29th 2019.

The reason given was: No longer maintained

The author has suggested example42-tp as its replacement.

Start using this module

Documentation

example42/monit — version 2.1.1 Apr 19th 2019

Deprecation notice

This module was designed for Puppet versions 2 and 3. It should work also on Puppet 4 but doesn't use any of its features.

The current Puppet 3 compatible codebase is no longer actively maintained by example42.

Still, Pull Requests that fix bugs or introduce backwards compatible features will be accepted.

Puppet module: monit

This is a Puppet module for monit based on the second generation layout ("NextGen") of Example42 Puppet Modules.

Made by Alessandro Franceschi / Lab42

Official site: http://www.example42.com

Official git repository: http://github.com/example42/puppet-monit

Released under the terms of Apache 2 License.

This module requires functions provided by the Example42 Puppi module (you need it even if you don't use and install Puppi)

For detailed info about the logic and usage patterns of Example42 modules check the DOCS directory on Example42 main modules set.

USAGE - Basic management

  • Install monit with default settings

      class { 'monit': }
    
  • Install a specific version of monit package

      class { 'monit':
        version => '1.0.1',
      }
    
  • Disable monit service.

      class { 'monit':
        disable => true
      }
    
  • Remove monit package

      class { 'monit':
        absent => true
      }
    

USAGE - Overrides and Customizations

  • Use custom sources for main config file

      class { 'monit':
        source => [ "puppet:///modules/example42/monit/monit.conf-${hostname}" , "puppet:///modules/example42/monit/monit.conf" ], 
      }
    
  • Use custom source directory for the whole configuration dir

      class { 'monit':
        source_dir       => 'puppet:///modules/example42/monit/conf/',
        source_dir_purge => false, # Set to true to purge any existing file not present in $source_dir
      }
    
  • Use custom template for main config file. Note that template and source arguments are alternative.

      class { 'monit':
        template => 'example42/monit/monit.conf.erb',
      }
    
  • Automatically include a custom subclass

      class { 'monit':
        my_class => 'example42::my_monit',
      }
    

USAGE - Example42 extensions management

  • Activate puppi (recommended, but disabled by default)

      class { 'monit':
        puppi    => true,
      }
    
  • Activate puppi and use a custom puppi_helper template (to be provided separately with a puppi::helper define ) to customize the output of puppi commands

      class { 'monit':
        puppi        => true,
        puppi_helper => 'myhelper', 
      }
    
  • Activate automatic monitoring (recommended, but disabled by default). This option requires the usage of Example42 monitor and relevant monitor tools modules

      class { 'monit':
        monitor      => true,
        monitor_tool => [ 'nagios' , 'monit' , 'munin' ],
      }
    
  • Activate automatic firewalling. This option requires the usage of Example42 firewall and relevant firewall tools modules

      class { 'monit':       
        firewall      => true,
        firewall_tool => 'iptables',
        firewall_src  => '10.42.0.0/24',
        firewall_dst  => $ipaddress_eth0,
      }
    

CONTINUOUS TESTING

Travis {}[https://travis-ci.org/example42/puppet-monit]