zabbix
Version information
This version is compatible with:
- Puppet Enterprise 3.x
- Puppet >= 3.0.0 < 5.0.0
- Archlinux , , , , , , , , , , ,
Start using this module
Add this module to your Puppetfile:
mod 'puppet-zabbix', '2.3.0'
Learn more about managing modules with a PuppetfileDocumentation
#puppet-zabbix
Continuous Integration status:
####Table of Contents
- Overview
- Upgrade
- [to 1.0.0] (#100)
- [to 2.0.0] (#200)
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with the zabbix module
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Contributors
- Notes
##Overview
This module contains the classes for installing and configuring the following zabbix components:
- zabbix-server
- zabbix-agent
- zabbix-proxy
- zabbix-javagateway
- zabbix-sender
This readme will contain all basic information to get you started. Some more information can be found on the github wiki, location: https://github.com/voxpupuli/puppet-zabbix/wiki
##Module Description When using this module, you can monitor your whole environment with zabbix. It can install the various zabbix components like the server and agent, but you will also be able to install specific "userparameter" file which zabbix can use for monitoring.
With the 0.4.0 release, you can - when you have configured exported resources - configure agents and proxies in the webinterface. So when you add an zabbix::agent to an host, it first install the agent onto the host. It will send some data to the puppetdb and when puppet runs on the zabbix-server it will create this new host via the zabbix-api.
Be aware when you have a lot of hosts, it will increase the puppet runtime on the zabbix-server host. It will check via the zabbix-api if hosts exits and costs time.
This module make uses of this gem: https://github.com/express42/zabbixapi With this gem it is possible to create/update hosts/proxy in ruby easy.
##Upgrade ###1.0.0 With release 1.0.0 the zabbix::server class is split into 3 classes:
- zabbix::web
- zabbix::server
- zabbix::database
Now you can use 3 machines for each purpose. This is something for the bigger environments to spread the load.
When upgrading from 0.x.x to 1.x.x, be aware of the following changes:
- Choose the correct zabbix setup for your environment *:
- Single node
- Multi node
- Path changes for the database ".done" file. Create the following files in /etc/zabbix/:
- /etc/zabbix/.schema.done
- /etc/zabbix/.images.done
- /etc/zabbix/.data.done
- Rename of the following parameters:
- dbtype --> database_type
- dbhost --> database_host
- dbuser --> database_user
- dbpass --> database_password
- dbschema --> database_schema
- dbname --> database_name
- dbsocket --> database_socket
- dbport --> database_port
* check this document/paragraph how to setup your environment. There were multiple changes to make this work (Like moving parameters to other (new) classes).
In case I missed something, please let me know and will update this document.
###2.0.0 Altough this is an major update, there is only one small change that we need to discuss and is specifically for the Zabbix Proxy.
The following properties for the zabbix::proxy needs to have the sizes:
- vmwarecachesize
- cachesize
- historycachesize
- historytextcachesize
Before 2.0.0 these could be used with an single integer, as in the template was hardcoded the 'M'. With release 2.0.0 you'll have to use the correct full size like: 8M, 16M or 2G.
##Setup As this puppet module contains specific components for zabbix, you'll need to specify which you want to install. Every zabbix component has his own zabbix:: class. Here you'll find each component.
###Setup zabbix-server This will install an basic zabbix-server instance. You'll have to decide if you want to run everything on a single host or multiple hosts. When installing on a single host, the 'zabbix' class can be used. When you want to use more than 1 host, you'll need the following classes:
- zabbix::web
- zabbix::server
- zabbix::database
You can see at "usage" in this documentation how all of this can be achieved.
You will need to supply one parameter: zabbix_url. This is the url on which the zabbix instance will be available. With the example at "setup", the zabbix webinterface will be: http://zabbix.example.com.
When installed succesfully, zabbix web interface will be accessable and you can login with the default credentials:
Username: Admin Password: zabbix
##Usage The following will provide an basic usage of the zabbix components.
###Usage zabbix-server
The zabbix-server can be used in 2 ways:
- one node setup
- multiple node setup.
The following is an example for using the PostgreSQL as database:
node 'zabbix.example.com'
class { 'apache':
mpm_module => 'prefork',
}
include apache::mod::php
class { 'postgresql::server': }
class { 'zabbix':
zabbix_url => 'zabbix.example.com',
}
}
When you want to make use of an MySQL database as backend:
node 'zabbix.example.com'
class { 'apache':
mpm_module => 'prefork',
}
include apache::mod::php
class { 'mysql::server': }
class { 'zabbix':
zabbix_url => 'zabbix.example.com',
database_type => 'mysql',
}
}
Everything will be installed on the same server. There is also an possibility to seperate the components, please check the following wiki: https://github.com/voxpupuli/puppet-zabbix/wiki/Multi-node-Zabbix-Server-setup
###Usage zabbix-agent
Basic one way of setup, wheter it is monitored by zabbix-server or zabbix-proxy:
class { 'zabbix::agent':
server => '192.168.20.11',
}
###Usage zabbix-proxy
Like the zabbix-server, the zabbix-proxy can also be used in 2 ways:
- single node
- multiple node
The following is an example for using the PostgreSQL as database:
node 'proxy.example.com'
class { 'postgresql::server': }
class { 'zabbix::proxy':
zabbix_server_host => '192.168.20.11',
database_type => 'postgresql',
}
}
When you want to make use of an MySQL database as backend:
node 'proxy.example.com'
class { 'mysql::server': }
class { 'zabbix::proxy':
zabbix_server_host => '192.168.20.11',
database_type => 'mysql',
}
}
When you want to make use of an sqlite database as backend:
class { 'zabbix::proxy':
zabbix_server_host => 'zabbix.example.com',
database_type => 'sqlite',
database_name => '/tmp/database',
}
You'll have to specify the location to the file in the database_name
parameter. Zabbix should have write access to the file/directory.
Everything will be installed on the same server. There is also an possibility to seperate the components, please check the following wiki: https://github.com/voxpupuli/puppet-zabbix/wiki/Multi-node-Zabbix-Proxy-setup
###Usage zabbix-javagateway
The zabbix-javagateway can be used with an zabbix-server or zabbix-proxy. You'll need to install it on an server. (Can be together with zabbix-server or zabbix-proxy, you can even install it on a sperate machine.). The following example shows you to use it on a seperate machine.
node server05.example.com {
# My ip: 192.168.20.15
class { 'zabbix::javagateway': }
}
When installed on seperate machine, the zabbix::server configuration should be updated by adding the javagateway
parameter.
node server01.example.com {
class { 'zabbix::server':
zabbix_url => 'zabbix.example.com',
javagateway => '192.168.20.15',
}
}
Or when using with an zabbix-proxy:
node server11.example.com {
class { 'zabbix::proxy':
zabbix_server_host => '192.168.20.11',
javagateway => '192.168.20.15',
}
}
###Usage zabbix-sender
The zabbix-sender installation is quite simple and straightforward:
include zabbix::sender
###Usage zabbix-userparameters Using an 'source' file:
zabbix::userparameters { 'mysql':
source => 'puppet:///modules/zabbix/mysqld.conf',
}
Or for example when you have just one entry:
zabbix::userparameters { 'mysql':
content => 'UserParameter=mysql.ping,mysqladmin -uroot ping | grep -c alive',
}
Using an LLD 'script' file:
zabbix::userparameters { 'lld_snort.sh':
script => 'puppet:///modules/zabbix/lld_snort.sh',
}
When you are using Hiera or The Foreman, you can use it like this:
---
classes:
zabbix::userparameter:
data:
mongo:
source: puppet:///modules/zabbix/mongo.conf
Content of the mongo.conf:
UserParameter=mongo.coll.count[*],echo "db.setSlaveOk();db.getCollection('$1').count()" | /opt/mongo/bin/mongo processor | sed -n 3p
UserParameter=mongo.db.queries,echo "db.currentOp().inprog.length" | /opt/mongo/bin/mongo processor | sed -n 3p
Screenshot from The Foreman (With thanks to "inspired-geek" )
When running the puppet-agent command, it will install the mongo.conf file on the host.
###Usage zabbix-template
With the 'zabbix::template' define, you can install Zabbix templates via the API. You'll have to make sure you store the XML file somewere on your puppet server or in your module.
Please be aware that you can only make use of this feature when you have configured the module to make use of exported resources.
You can instal the MySQL template xml via the next example:
zabbix::template { 'Template App MySQL':
templ_source => 'puppet:///modules/zabbix/MySQL.xml'
}
##Reference There are some overall parameters which exists on all of the classes:
zabbix_version
: You can specify which zabbix release needs to be installed. Default is '3.0'.manage_firewall
: Wheter you want to manage the firewall. If true, iptables will be configured to allow communications to zabbix ports. (Default: False)manage_repo
: If zabbix needs to be installed from the zabbix repositories (Default is true). When you have your own repositories, you'll set this to false. But you'll have to make sure that your repositorie is installed on the host.
The following is only availabe for the following classes: zabbix::web, zabbix::proxy & zabbix::agent
manage_resources
: As of release 0.4.0, when this parameter is set to true (Default is false) it make use of exported resources. You'll have an puppetdb configured before you can use this option. Information from the zabbix::agent, zabbix::proxy and zabbix::userparameters are able to export resources, which will be loaded on the zabbix::server.database_type
: Which database is used for zabbix. Default is postgresql.manage_database
: When the parameter 'manage_database' is set to true (Which is default), it will create the database and loads the sql files. Default the postgresql will be used as backend, mentioned in the params.pp file. You'll have to include the postgresql (or mysql) module yourself, as this module will require it.
###Reference zabbix (init.pp) This is the class for installing everything on a single host and thus all parameters described earlier and those below can be used with this class.
###Reference zabbix-web
zabbix_url
: This is the url on which Zabbix should be available. Please make sure that the entry exists in the DNS configuration.zabbix_timezone
: On which timezone the machine is placed. This information is needed for the apache virtual host.manage_vhost
: Will create an apache virtual host. Default is true.apache_use_ssl
: Will create an ssl vhost. Also nonssl vhost will be created for redirect nonssl to ssl vhost.apache_ssl_cert
: The location of the ssl certificate file. You'll need to make sure this file is present on the system, this module will not install this file.apache_ssl_key
: The location of the ssl key file. You'll need to make sure this file is present on the system, this module will not install this file.apache_ssl_cipher
: The ssl cipher used. Cipher is used from: https://wiki.mozilla.org/Security/Server_Side_TLS.apache_ssl_chain
: The ssl_chain file. You'll need to make sure this file is present on the system, this module will not install this file.apache_php_max_execution_time
: Max execution time for php.apache_php_memory_limit
: PHP memory size limit.apache_php_upload_max_filesize
: HP maximum upload filesize.apache_php_max_input_time
: Max input time for php.apache_php_always_populate_raw_post_data
: Default: -1zabbix_api_user
: Username of user in Zabbix which is able to create hosts and edit hosts via the zabbix-api. Default: Adminzabbix_api_pass
: Password for the user in Zabbix for zabbix-api usage. Default: zabbixzabbix_template_dir
: The directory where all templates are stored before uploading via APIldap_cacert
: The location of the CA Cert to be used for Zabbix LDAP authentication. The module will not install this file so it must be present on the system.ldap_clientcrt
: The location of the Client Cert to be used for Zabbix LDAP authentication. The module will not install this file so it must be present on the system.ldap_clientkey
: The location of the Client Key to be used for Zabbix LDAP authentication. The module will not install this file so it must be present on the system.
There are some more zabbix specific parameters, please check them by opening the manifest file.
###Reference zabbix-server
database_path
: When database binaries are not in $PATH, you can use this parameter to appenddatabase_path
to $PATHtlscafile
: Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification.tlscertfile
: Full pathname of a file containing the server certificate or certificate chain.tlscrlfile
: Full pathname of a file containing revoked certificates.tlskeyfile
: Full pathname of a file containing the server private key.
There are some more zabbix specific parameters, please check them by opening the manifest file.
###Reference zabbix-agent
server
: This is the ipaddress of the zabbix-server or zabbix-proxy.tlsaccept
: What incoming connections to accept from Zabbix server. Used for a passive proxy, ignored on an active proxy.tlscafile
: Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification.tlscertfile
: Full pathname of a file containing the proxy certificate or certificate chain.tlsconnect
: How the proxy should connect to Zabbix server. Used for an active proxy, ignored on a passive proxy.tlscrlfile
: Full pathname of a file containing revoked certificates.tlskeyfile
: Full pathname of a file containing the proxy private key.tlspskfile
: Full pathname of a file containing the pre-shared key.tlspskidentity
: Unique, case sensitive string used to identify the pre-shared key.tlsservercertissuer
: Allowed server certificate issuer.tlsservercertsubject
: Allowed server certificate subject.
The following parameters is only needed when manage_resources
is set to true:
monitored_by_proxy
: When an agent is monitored via an proxy, enter the name of the proxy. The name is found in the webinterface via: Administration -> DM. If it isn't monitored by an proxy ormanage_resources
is false, this parameter can be empty.agent_use_ip
: Default is set to true. Zabbix server (or proxy) will connect to this host via ip instead of fqdn. When set to false, it will connect via fqdn.zbx_group
: Name of the hostgroup on which the agent will be installed. There can only be one hostgroup defined and should exists in the webinterface. Default: Linux serverszbx_templates
: Name of the templates which will be assigned when agent is installed. Default (Array): 'Template OS Linux', 'Template App SSH Service'
There are some more zabbix specific parameters, please check them by opening the manifest file.
###Reference zabbix-proxy
zabbix_server_host
: The ipaddress or fqdn of the zabbix server.database_path
: When database binaries are not in $PATH, you can use this parameter to appenddatabase_path
to $PATHtlsaccept
: What incoming connections to accept from Zabbix server. Used for a passive proxy, ignored on an active proxy.tlscafile
: Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification.tlscertfile
: Full pathname of a file containing the proxy certificate or certificate chain.tlsconnect
: How the proxy should connect to Zabbix server. Used for an active proxy, ignored on a passive proxy.tlscrlfile
: Full pathname of a file containing revoked certificates.tlskeyfile
: Full pathname of a file containing the proxy private key.tlspskfile
: Full pathname of a file containing the pre-shared key.tlspskidentity
: Unique, case sensitive string used to identify the pre-shared key.tlsservercertissuer
: Allowed server certificate issuer.tlsservercertsubject
: Allowed server certificate subject.
The following parameters is only needed when manage_resources
is set to true:
use_ip
: Default is set to true.zbx_templates
: List of templates which are needed for the zabbix-proxy. Default: 'Template App Zabbix Proxy'mode
: Which kind of proxy it is. 0 -> active, 1 -> passive
There are some more zabbix specific parameters, please check them by opening the manifest file.
###Reference zabbix-javagateway There are some zabbix specific parameters, please check them by opening the manifest file.
###Reference zabbix-userparameters
source
: File which holds several userparameter entries.content
: When you have 1 userparameter entry which you want to install.script
: Low level discovery (LLD) script.script_ext
: The script extention. Should be started with the dot. Like: .sh .bat .pytemplate
: When you use exported resources (when manage_resources on other components is set to true) you'll can add the name of the template which correspondents with the 'content' or 'source' which you add. The template will be added to the host.script_dir
: Whenscript
is used, this parameter can provide the directly where this script needs to be placed. Default: '/usr/bin'
###Reference zabbix-template
templ_name
: The name of the template. This name will be found in the Web interface.templ_source
: The location of the XML file wich needs to be imported.
##limitations The module is only supported on the following operating systems:
Zabbix 3.0:
- CentOS 7.x
- Amazon 7.x
- RedHat 7.x
- OracleLinux 7.x
- Scientific Linux 7.x
- Ubuntu 14.04
- Debian 8
Zabbix 2.4:
- CentOS 6.x, 7.x
- Amazon 6.x, 7.x
- RedHat 6.x, 7.x
- OracleLinux 6.x, 7.x
- Scientific Linux 6.x, 7.x
- Ubuntu 12.04 14.04
- Debian 7
Zabbix 2.2:
- CentOS 5.x, 6.x
- RedHat 5.x, 6.x
- OracleLinux 5.x, 6.x
- Scientific Linux 5.x, 6.x
- Ubuntu 12.04
- Debian 7
- xenserver 6
Zabbix 2.0:
- CentOS 5.x, 6.x
- RedHat 5.x, 6.x
- OracleLinux 5.x, 6.x
- Scientific Linux 5.x, 6.x
- Ubuntu 12.04
- Debian 6, 7
- xenserver 6
This module is supported on both the community as the Enterprise version of Puppet.
Please be aware, that when manage_resources is enabled, it can increase an puppet run on the zabbix-server a lot when you have a lot of hosts.
##Contributors
ericsysmin will be helping and maintaining this puppet module. In Github terms he is an Collaborator. So don't be suprised if he acceps/rejects Pull Requests and comment in issues.
The following have contributed to this puppet module:
- Suff
- gattebury
- sq4ind
- nburtsev
- actionjack
- karolisc
- lucas42
- f0
- mmerfort
- genebean
- meganuke19
- fredprod
- ericsysmin
- JvdW
- rleemorlang
- genebean
- exptom
- sbaryakov
- roidelapluie
- andresvia
- ju5t
- elricsfate
- IceBear2k
- altvnk
- rnelson0
- hkumarmk
- Wprosdocimo
- 1n
- szemlyanoy
- Wprosdocimo
- sgnl05
- hmn
- BcTpe4HbIu
- mschuett
- claflico
- bastelfreak
- Oyabi
- akostetskiy
- DjxDeaf
- tcatut
- inspired-geek
- ekohl
- z3rogate
- mkrakowitzer
- eander210
- hkumarmk
- ITler
- slashr00t
- channone-arif-nbcuni
- BcTpe4HbIu
- vide
Many thanks for this! (If I have forgotten you, please let me know and put you in the list of fame. :-))
##Note ###Standard usage
- Not specified as required but for working correctly, the epel repository should be available for the 'fping'|'fping6' packages.
- Make sure you have sudo installed and configured with: !requiretty.
- Make sure that selinux is permissive or disabled.
###When using exported resources
At the moment of writing, the puppet run will fail one or more times when manage_resources
is set to true when you install an fresh Zabbix server. It is an issue and I'm aware of it. Don't know yet how to solve this, but someone suggested to try puppet stages and for know I haven't made it work yet.
- Please be aware, that when
manage_resources
is enabled, it can increase an puppet run on the zabbix-server a lot when you have a lot of hosts. - First run of puppet on the zabbix-server can result in this error:
Error: Could not run Puppet configuration client: cannot load such file -- zabbixapi
Error: Could not run: can't convert Puppet::Util::Log into Integer
See: http://comments.gmane.org/gmane.comp.sysutils.puppet.user/47508, comment: Jeff McCune | 20 Nov 20:42 2012
This specific issue is a chicken and egg problem where by a provider needs a gem, but the catalog run itself is the thing that provides the gem dependency. That is to say, even in Puppet 3.0 where we delay loading all of the providers until after pluginsync finishes, the catalog run hasn't yet installed the gem when the provider is loaded.
The reason I think this is basically a very specific incarnation of #6907 is because that ticket is pretty specific from a product functionality perspective, "You should not have to run puppet twice to use a provider."
After another puppet run, it will run succesfully.
- On a Red Hat family server, the 2nd run will sometimes go into error:
Could not evaluate: Connection refused - connect(2)
When running puppet again (for 3rd time) everything goes fine.
Types in this module release
2016-5-08 Release 2.3.0
- fix typo/missing code in userparameters
- modulesync with voxpupuli defaults #214
- fix typo in zabbix_host provider #211
- Enhance spec testing #206 (By pull request: bastelfreak (Thanks!))
- Update rubocop #204 (By pull request: bastelfreak (Thanks!))
- Update rspec #203 (By pull request: bastelfreak (Thanks!))
- [WIP]Add archlinux #201 (By pull request: bastelfreak (Thanks!))
- Fix for: Web interface config file readable by all (contains unencrypted database password) #200
- there is no zabbix proxy package in zbx-3.0 #198 (By pull request: BcTpe4HbIu (Thanks!))
- Zabbix as default vhost #180 #196 (By pull request: szemlyanoy (Thanks!))
- fix wrong comment for configfrequency #192 (By pull request: BcTpe4HbIu (Thanks!))
- Add Zabbix sender support #195 (By pull request: vide (Thanks!))
- Update zabbixapi gem to 2.4.7 form Zabbix 3.0
- ericsysmin is added as an Collaborator. He will help maintain this puppet module.
2016-03-06 Release 2.2.0
- Adjust server config and databases sqls for 3.0 #167 (By pull request: slashr00t (Thanks!))
- Added Zabbix Proxy, Agent, Server, 3.0 support and Pacemaker exclusions #174 (By pull request: ericsysmin (Thanks!))
- removed notify, forgot to take it out when I was troubleshooting #173 (By pull request: ericsysmin (Thanks!))
- Patch 6 #171 (By pull request: ericsysmin (Thanks!))
- TLS Support for Zabbix 3.0 #169 (By pull request: ericsysmin (Thanks!))
- Added rspec tests for Zabbix 3.0
- Fix for: Issues with RHEL7 repos configuration #183.
- Make types run in puppet 4 #182 (By pull request: ITler (Thanks!))
- Added documentation for Zabbix::Proxy regaring sqlite3 database.
- Zabbix 3.0 Proxy Postgres DB Schema Using Incorrect File #186 (By request: channone-arif-nbcuni (Thanks!))
- Moved some documentation to the github wiki.
2016-02-09 Release 2.1.1
- Make Zabbix module compile on puppet 4.x AIO. #164 (By pull request: ITler (Thanks!))
- Fix for Repo is always added #148
2016-02-02 Release 2.1.0
- Removed a debug entry #156 (By pull request: hkumarmk (Thanks!))
- Add Puppet Forge Version and Downloads badges #163 (By pull request: rnelson0 (Thanks!))
- Travis CI setup: ensure all rspec tests pass #162 (By pull request: rnelson0 (Thanks!))
- Update proxy.pp, fix Error: ...install zabbix-proxy- .. #159 (By pull request: subkowlex (Thanks!))
- Puppetgem #158 (By pull request: rnelson0 (Thanks!))
Release 2016-01-31 2.0.0
- wdijkerman-zabbix works with puppet 4
- Fix for: Server and Proxy templates are inconsistent #144
- fixed SSL server template options for 2.2 #141 (By pull request: IceBear2k (Thanks!))
- fix syntax error #139 (By pull request: mkrakowitzer (Thanks!))
- Allow agent to listen on * #138 (By pull request: ekohl (Thanks!))
- enable apache_php_max_input_vars #137 (By pull request: bastelfreak (Thanks!))
- Fix typo in zabbix-userparameters reference #136 (By pull request: sgnl05 (Thanks!))
- Listen on all IPs #133 (By pull request: z3rogate (Thanks!))
- tap0 or tun0 (OpenVPN interfaces) interface as listenip #132 (By pull request: z3rogate (Thanks!))
- fixed typo for comment mysql #145 (By pull request: eander210 (Thanks!))
- Updated the listen_ip for proxy so it same as for agent.
- allow serveractive to be optional #146 (By pull request: ericsysmin (Thanks!))
- Allow agent_serveractive value to be blank #147 (By pull request: ericsysmin (Thanks!))
- Added support for adding LDAP certificate location to Zabbix Web. Upd… #150 (By pull request: elricsfate (Thanks!))
- Added zabbix_template_host type #154 (By pull request: hkumarmk (Thanks!))
- Type to manage zabbix application #155 (By pull request: hkumarmk (Thanks!))
2015-11-07 Release 1.7.0
- misspelled parameter path #116 (By pull request: karolisc (Thanks!))
- Update template.pp #121 (By pull request: claflico (Thanks!))
- add support for CloudLinux #122 (By pull request: bastelfreak (Thanks!))
- Fping wrong path in debian #124 (By pull request: Oyabi (Thanks!))
- refactoring of repo.pp #126 (By pull request: bastelfreak (Thanks!))
- Added supporting new Zabbix params #128 (By pull request: akostetskiy (Thanks!))
- Generalise the zabbix_url #129 (By pull request: DjxDeaf (Thanks!))
2015-08-21 Release 1.6.0
- Pass manage_repo and zabbix_repo to repo.pp and prevent double include #110 (By pull request: mmerfort (Thanks!))
- Add "eno" to interface name matching #104 (By pull request: sgnl05 (Thanks!))
- use the new puppetlabs-apt version 2.x module #103 (By pull request: hmn (Thanks!))
- Fix name startvmwarecollector -> startvmwarecollectors #102 (By pull request: BcTpe4HbIu (Thanks!))
- Custom apache IP and port #99 (By pull request: mschuett (Thanks!))
- Feature Request: add charset/collate option during a mysql db resource creation #107
- Added support Debian 8
- Fixed some rpsec tests
- Fixed some puppet-lint identation warnings
- Updated the zabbixapi gem install with recent versions
2015-06-08 Release 1.5.0
- Fix for: Inherting params #93
- Fix for: new postgresql instance #91; Also update metadata for postgresl module version
- Fix for: Need to overide php_values #89
- 2nd fix for: Zabbix-proxy install database population #62. Also for postgresql now.
- Added support to Amazon Linux with epel 6. #96 (By pull request: Wprosdocimo (Thanks!))
- import templates and create hostgroup if missing #95 (By pull request: 1n (Thanks!))
- Added Support For Zapache monitoring script #94 (By pull request: elricsfate (Thanks!))
- merge of hiera hashes from entire hierarchy #98 (By pull request: szemlyanoy (Thanks!))
- Added property script_ext for: File extensions of Userparameters scripts #97
- Updated documentation in README.md
2015-05-18 Release 1.4.0
- Adding "apt" as dependency.
- Adding 'script_dir' parameter for userparameters define.
- Fix documentation: iptables is set to false (not true).
- Fix illegal comma separated argument list #81 (By pull request: IceBear2k (Thanks!))
- Fixes #80 setting Hostname and HostnameItem causes a warning on agentd s... #82 (By pull request: f0 (Thanks!))
- Allow to not purge include dir. #79 (By pull request: altvnk (Thanks!))
- Correct typo in 'manage_resources' documentation. #77 (By pull request: rnelson0 (Thanks!))
- Added zabbix_hostgroup #87 (By pull request: hkumarmk (Thanks!))
2015-04-08 Release 1.3.0
- bugfix for vhosts in apache 2.4 #67 (By pull request: ju5t (Thanks!))
- Update apt key to full 40characters #66 (By pull request: exptom (Thanks!))
- rename ListenIp => ListenIP (By pull request: sbaryakov (Thanks!))
- Fix manage_repo parameter on the zabbix class (By pull request: roidelapluie (Thanks!))
- minor typo (By pull request: andresvia (Thanks!))
- better default parameter for userparameter (By pull request: sbaryakov (Thanks!))
- Fix for: Multi-node Setup: Web class does not properly configure database port #69
- Fix for: Zabbix-proxy install database population #62
2015-02-26 Release 1.2.0
- Support for RedHat/CentOS/OracleLinux 7
- Fixed bug with listenip & add lxc interface #46 (By pull request: meganuke19 (Thanks!))
- Bad syntax in manifests/proxy.pp #50 (By pull request: fredprod (Thanks!))
- Fix agent listenip #52 (By pull request: JvdW (Thanks!))
- Fix in params.pp with default parameter of zabbix proxy for ubuntu #56 (By pull request: fredprod (Thanks!))
- notify zabbix-agent service when userparameters change #57 (By pull request: rleemorlang (Thanks!))
- Fix for: "Cannot Load Such File -- zabbixapi" despite installation #54
- Fix for: correct order, so 1 puppet run installs the proxy
2015-01-24 Release 1.1.0
- Fix name of agent config file in params.pp #39 (By pull request: mmerfort (Thanks!))
- Unable to create host with zabbixapi - Invalid params #37 (By pull request: genebean (Thanks!))
- setting manage_repo to false breaks server install #38 (By pull request: genebean (Thanks!))
- listenip statement didn't work with 'eth' addresses" manifests/agent.pp
- Fix for: rpsec tests to work with latest version.
- Fix for: (mysql and postgresql) must be quotted as it contains special characters
- Fix for: allow setting location of psql #44
- Fix: for the last identation error in manifests/web.pp.
2015-01-12 Release 1.0.1
- remove hardcoded config file paths for server, proxy and agent #34 (By pull request: f0 (Thanks!))
- ZABBIX proxy and ZABBIX server service names are now customizable / Allow changing the path to the database schema files #35 (By pull request: f0 (Thanks!))
- allow custom owner and group for zabbix server config, #36 (By pull request: f0 (Thanks!))
- Fixed some puppet-lint messages (Was using old puppet-lint version)
2015-01-02 Release 1.0.0
- Split Zabbix Server Class into Components. See the documentation
readme.md
for more information. - Renamed some parameters. Mostly the database parameters, from
db
todatabase_
- Changed the paths for the .done files to /etc/zabbix/. This makes upgrading zabbix components a lot easier.
- Added zabbix_package_state parameter. You can choose present or latest.
- Included the puppetlabs/ruby for development packages when installing the zabbixapi gem.
- Add support for low level discovery(LLD) scripts #27 (By pull request: karolisc (Thanks!))
- Remove execute bit from .conf files #26 (By pull request: karolisc (Thanks!))
- Wrong name in zabbix::userparameters resource example. #25 (By pull request: karolisc (Thanks!))
- Fix for: Module fails with future parser enabled #29
- Fix for: Wrong fping path on Ubuntu 14.04 #28
- fixed puppet-lint message in userparameter.pp
- Add support for debian sid (just use wheezy package) #30 (By pull request: lucas42 (Thanks!))
- Fox for: Update apache_ssl_cipher list #31 (And by pull request: karolisc (Thanks!))
2014-12-09 Release 0.6.1
- Add repository for debian running on a raspberry pi (By pull request: lucas42 (Thanks!))
- fixed puppet-lint messages
2014-12-06 Release 0.6.0
- Add support for sqlite (by pull request: actionjack (Thanks!))
- Updated documentation for correct usage server and proxy (Thanks for noticing karolisc!)
- Don't assume db_host will be localhost in postgresql.pp #20 (By pull request: lucas42 (Thanks!))
- added class zabbix::userparameter for using userparameters define in Hiera or The Foreman
- Removed the '/24' in zabbix::agent for firewall.
2014-10-30 Release 0.5.1
- Added apache_ssl_chain as parameter for zabbix::server
- zabbix.conf.php.erb wrong zbx name (https://github.com/dj-wasabi/puppet-zabbix/issues/9)
- fix for host template management (Fixed by pull request: burtsev (Thanks!))
2014-10-11 Release 0.5.0
- zabbixapi gem is installed by version.
- Possibility to create SSL vhost. (As requested: https://github.com/dj-wasabi/puppet-zabbix/issues/8)
- Removed symlink in spec/fixtures/modules dir and updated .fixtures file for this.
2014-09-11 Release 0.4.1
- Added support van Zabbix 2.4
- Added Ubuntu 14.04
2014-08-22 Release 0.4.0
- Rewrote the readme.
- Module can make use of "Exported resources" when
manage_resources
is set to true. The zabbix-server can automatically configure agents and directly monitor the agents. It will make use of the zabbix-api. - Also possible for the listenip parameter to specificy an 'eth?|bond?' option. It will find out what ipaddress it is and uses this as the ListenIP in the zabbix configuration file. Can be handy when having multiple network interfaces.
2014-08-01 Release 0.3.1
- Added support for Puppet Enterprise 3.2 and 3.3
2014-07-19 Release 0.3.0
- Added repository for scientific (Thanks to: gattebury)
- Added repository for Xenserver (Thanks to: sq4ind)
2014-06-18 Release 0.2.0
- Added rspec test for zabbix::agent
- Added rspec test for zabbix::repo
- Added rspec test for zabbix::proxy
- Added rspec test for zabbix::server
- Added rspec test for zabbix::database{mysql,postgresql}
- Added rspec test for zabbix::userparameters
- Added rspec test for zabbix::javagateway
- zabbix::userparameters fixed via pull request github (By 'suff') --> Thanks!
- Removed some documented settings
- nodeid wasn't working with zabbix_server.conf template
2014-04-17 Release 0.1.0
- Added manage_repo parameter. If set to true, it will install the apt/yum repository.
- Updated module for support Ubuntu (12.x).
- Updated module for support Debian (6, 7).
- Updated module for support Oracle Linux (5, 6).
2014-03-31 Release 0.0.3
- Added parameter: manage_vhost for creating vhost (Default: true)
- Added parameter: manage_firewall for creating firewall rules
- Added zabbix::javagateway class for installing the Zabbix Java Gateway
- Renaming parameters javagateway_host to javagateway and javagateway_port to javagatewayport for zabbix::proxy (Same naming as the zabbix::server).
2014-03-28 Release 0.0.2
- MySQL can be used as database back-end.
- Services started at boot.
- Vhost creation, need 1 parameter for zabbix-server: zabbix_url.
- Updated the readme.md
2014-03-18 Release 0.0.1
- Initial working version. Installing of the
- zabbix-server
- zabbix-agent
- zabbix-proxy
- Possibility to add userparameters for the zabbix-agent.
Dependencies
- puppetlabs/postgresql (>= 4.0.0)
- puppetlabs/stdlib (>= 4.1.0)
- puppetlabs/mysql (>= 2.0.0)
- puppetlabs/apache (>= 1.0.0)
- puppetlabs/firewall (>= 1.0.0)
- puppetlabs/ruby (>= 0.4.0)
- puppetlabs/pe_gem (>= 0.1.0)
- puppetlabs/apt (>= 2.0.0)
Copyright (C) 2015 Werner Dijkerman wdijkerman-zabbix can be contacted at: ikben@werner-dijkerman.nl Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.