Chef Cookbook: Zabbix
Find a file
2017-02-07 01:02:03 -05:00
attributes Initial commit 2017-02-07 01:02:03 -05:00
files/default/traps Initial commit 2017-02-07 01:02:03 -05:00
recipes Initial commit 2017-02-07 01:02:03 -05:00
spec Initial commit 2017-02-07 01:02:03 -05:00
templates/default Initial commit 2017-02-07 01:02:03 -05:00
test Initial commit 2017-02-07 01:02:03 -05:00
.gitignore Initial commit 2017-02-07 01:02:03 -05:00
.kitchen.vagrant.yml Initial commit 2017-02-07 01:02:03 -05:00
.kitchen.yml Initial commit 2017-02-07 01:02:03 -05:00
Berksfile Initial commit 2017-02-07 01:02:03 -05:00
chefignore Initial commit 2017-02-07 01:02:03 -05:00
Gemfile Initial commit 2017-02-07 01:02:03 -05:00
local-vagrantfile.rb Initial commit 2017-02-07 01:02:03 -05:00
metadata.rb Initial commit 2017-02-07 01:02:03 -05:00
README.md Initial commit 2017-02-07 01:02:03 -05:00

Zabbix Cookbook

This cookbook installs, manages, and handles Zabbix for monitoring systems health and system metrics. It also handles trap script auto-discovery based on recipe inclusion and tags, as well as auto-registration metadata.

The way auto-discovery works is, for example, if the openldap recipe is included in the run_list, the zabbix::trap_scripts will set up the variables used to add certain trap scripts to the monitored system, for use in:/etc/zabbix/trap.d/{live,daily}/

Optionally, in case a recipe is incomplete or not in use, you can manually enable a trap agent by use of tags on a per-node basis as well, using the node tags as such:

{
  "name": "some.node.name",
  "chef_environment": "_default",
  "normal": {
    "tags": [
      "httpd",
      "openldap"
    ]
  },
  "run_list": [
    "recipe[zabbix]"
  ]
}

This allows for fully automated, and manual designation of agents required for monitoring on every system.

Available tags for manual override are as follows:

httpd:  	Apache HTTPD
openldap:	OpenLDAP
mongodb:	MongoDB Database Server
tomcat:		Tomcat 6 Server