Automating Zabbix with Puppet (Werner Dijkerman / 26-11-2015)
•Download as PPTX, PDF•
0 likes•3,210 views
This document discusses using Puppet to automate the configuration and management of Zabbix monitoring systems. It provides examples of Puppet code that can be used to install, configure, and manage Zabbix servers, proxies, agents, templates, and other components. It also discusses using Puppet to define Zabbix resources, templates, and user parameters as well as integrating Puppet and Zabbix through the Zabbix API and PuppetDB.
Report
Share
Recommended for you
Recommended for you
Recommended for you
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Automating Zabbix with Puppet (Werner Dijkerman / 26-11-2015)
Similar to Automating Zabbix with Puppet (Werner Dijkerman / 26-11-2015) (20)
Recently uploaded
Recently uploaded (20)
Automating Zabbix with Puppet (Werner Dijkerman / 26-11-2015)
- 2. $ whoami Werner Dijkerman Work Current: System Engineer @ iWelcome Previous: Promedico, Bol.com Private 34 years old, Married (Francina), 2 cats (Janice & Vlokje) TV shows, movies, Music & Monitoring www.werner-dijkerman.nl @djwasabiman
- 3. wdijkerman-zabbix Started April 2014, 36 committers, 74 pull requests
- 4. Puppet Configuration management utility The user describes system resources and their state, either using Puppet's declarative language or a Ruby DSL (domain-specific language). • Automatically installs /configures systems / applications • Keep all systems in sync
- 5. Puppet package { 'zabbix-agent': ensure => present, } service { 'zabbix-agent': ensure => running, require => Package['zabbix-agent'] }
- 6. file { '/etc/zabbix/zabbix_server.conf': ensure => present, owner => 'zabbix', group => 'zabbix', mode => '0640', notify => Service['zabbix-server'], require => Package['zabbix-server-mysql'], content => template('zabbix/zabbix_server.conf.erb'), } ### option: startpollers # number of pre-forked instances of pollers. # StartPollers=<%= @startpollers %>
- 7. zabbix::server What database? • PostgreSQL • MySQL What kind of setup? • Single node • Multi node
- 8. node 'zabbix.example.com' { class { 'apache': mpm_module => 'prefork', } include apache::mod::php class { 'postgresql::server':} class { 'zabbix': zabbix_url => 'zabbix.example.com', } }
- 9. class { 'zabbix': zabbix_url => 'zabbix.example.com', zabbix_version => '2.4', zabbix_timezone => 'Europe/Amsterdam', database_type => 'mysql', database_user => 'zabbix', database_password => 'V3ry5tr0ngP@$$0rd', apache_use_ssl => true, apache_ssl_cert => '/etc/httpd/conf.d/keys/zabbix_ssl.crt', apache_ssl_key => '/etc/httpd/conf.d/keys/zabbix_ssl.key', manage_resources => true, manage_database => true, manage_vhost => true, cachesize => '128M', startpollers => 10, timeout => 17, }
- 10. zabbix::proxy What database? • PostgreSQL • MySQL • Sqlite3 What kind of setup? • Single node • Multi node
- 11. node 'server11.example.com' { class { 'postgresql::client': } class { 'zabbix::proxy': zabbix_server_host => '192.168.20.11', manage_database => false, database_host => 'server12.example.com', database_name => 'zabbix-proxy', database_user => 'zabbix-proxy', database_password => 'zabbix-proxy', } } node 'server12.example.com' { class { 'postgresql::server': listen_addresses => '192.168.30.12' } class { 'zabbix::database': zabbix_type => 'proxy', zabbix_proxy_ip => '192.168.30.11', database_name => 'zabbix-proxy', database_user => 'zabbix-proxy', database_password => 'zabbix-proxy', } }
- 12. zabbix::javagateway node server05.example.com { class { 'zabbix::javagateway': } } For the zabbix::server (or zabbix::proxy) node server01.example.com { class { 'zabbix::server': zabbix_url => 'zabbix.example.com', javagateway => '192.168.20.15', } }
- 13. zabbix::agent class { 'zabbix::agent': server => '192.168.20.11', timeout => 10, include_dir => '/etc/zabbix/zabbix_agent.d', } 'server' parameter is ip/fqdn for the zabbix-server, or zabbix-proxy
- 14. zabbix::userparameters UserParameter=mysql.status[*],echo "show global status where Variable_name='$1';" | HOME=/var/lib/zabbix mysql -N | awk '{print $$2}’ UserParameter=mysql.ping,HOME=/var/lib/zabbix mysqladmin ping | grep -c alive UserParameter=mysql.version,mysql –V zabbix::userparameters { 'mysql': source => 'puppet:///modules/mysql/zabbix_mysqld.conf', template => 'Template App MySQL', }
- 15. Installing Template zabbix::template { 'Template App MySQL': templ_source => 'puppet:///modules/zabbix/MySQL.xml' } zabbix::template
- 16. manage_resources => true Puppetdb Storing puppet-agent related data in database. Zabbix Make use of the API Ruby gem: express42/zabbixapi
- 17. node 'database.example.com' { class { 'mysql::server':} class { 'zabbix::agent': server => '192.168.20.11', manage_resources => true, zbx_group => 'Linux Servers', zbx_templates => [ 'Template OS Linux', 'Template App SSH Service', 'My Awesome Template', ] } }