Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms


zabbix-agent (7) Versions 0.14.0

Installs/Configures Zabbix Agent

cookbook 'zabbix-agent', '~> 0.14.0'
cookbook 'zabbix-agent', '~> 0.14.0', :supermarket
knife cookbook site install zabbix-agent
knife cookbook site download zabbix-agent
Quality 44%

Chef Cookbook - zabbix-agent

CK Version Build Status Gitter

This cookbook installs and configures the zabbix-agent with sane defaults and very minimal dependancies.

Supported OS Distributions

  • RHEL/CentOS 6, 7
  • Ubuntu 10.04 12.04 14.04
  • Debian 6.0.10 7.8
  • (soon) fedora
  • (soon) opensuse
  • (planned) freebsd
  • (planned) Windows

Other similar versions will likely work as well but are not regularly tested.


If you have a supported OS, internet access, and a searchable DNS alias for "zabbix" that will resolve to your zabbix server this cookbook will work with no additional changes. Just include recipe[zabbix-agent] in your run_list.

Otherwise you will need to modify this to point to your zabbix server:

node['zabbix']['agent']['servers'] = ''


default['zabbix']['agent']['package']['repo_uri'] = ''
default['zabbix']['agent']['package']['repo_key'] = ''

or try one of the other install methods

Other recomended cookbooks

  • libzabbix - in development LWRPs to auto regester and setup monitoring for hosts
  • zabbix-server - install configure Zabbix server - planned
  • zabbix-web - install configure Zabbix web frontend - planned

zabbix_agentd.conf file

All attributes in the zabbix_agentd.conf file can be controlled from the:


attribute. This will require a change in attribute naming for upgrades from 0.9.0.

default['zabbix']['agent']['conf']['Timeout'] = '10'


  "default_attributes": {
    "zabbix": {
      "agent": {
        "conf": {
          "Server": [""],
          "Timeout": "10"

Default Install, Configure and run zabbix agent

Install packages from and run the Agent:

  "run_list": [

Selective Install or Install and Configure (don't start zabbix-agent)

Alternatively you can just install, or install and configure:

  "run_list": [

or json { "run_list": [ "recipe[zabbix-agent::configure]" ] }


Install Method options are:

node['zabbix']['agent']['install_method'] = 'package' # Default
node['zabbix']['agent']['install_method'] = 'source'
node['zabbix']['agent']['install_method'] = 'prebuild'
node['zabbix']['agent']['install_method'] = 'cookbook_file' # not yet implemented
node['zabbix']['agent']['install_method'] = 'chocolatey' # Default for Windows

# skip is preferred if no internet access when provisioning
# zabbix agent was already installed via chef during image bake process
node['zabbix']['agent']['install_method'] = 'skip'


node['zabbix']['agent']['version'] # Default 3.0.9


node['zabbix']['agent']['conf']['Server'] = ["",""]
    # defaults to zabbix
node['zabbix']['agent']['conf']['ServerActive'] = [""]

Package install

If you do not set any attributes you will get an install of zabbix agent version 3.0.9 with what should be a working configuration if your DNS has aliases for and your hosts search

Source install

If you do not specify source_url attributes for agent it will be set to download the specified branch and version from the official Zabbix source repository. If you want to upgrade later, you need to either nil out the source_url attributes or set them to the URL you wish to download from.


to install an alternative branch or tar file you can specify it here

node['zabbix']['agent']['source_url'] = ""

Prebuild install

The current latest prebuild is behind the source and packaged versions. You will need to set


to the version you wish to be installed.

Cookbook file install

This will install a provided package that can be included in the ./files directory of the cookbook itself and stored on the chef server.

Chocolatey install

Currently untested. Pull requests and kitchen tests desired.

Note :

A Zabbix agent running on the Zabbix server will need to : * use a different account than the one the server uses or it will be able to spy on private data. * specify the local Zabbix server using the localhost (, ::1) address.



The default recipe installs, configures and starts the zabbix_agentd.

You can control the agent install with the following attributes:

node['zabbix']['agent']['install_method'] = 'package' # Default

or node['zabbix']['agent']['install_method'] = 'source' or node['zabbix']['agent']['install_method'] = 'prebuild' or node['zabbix']['agent']['install_method'] = 'cookbook_file' # not yet implemented


Controls the service start/stop/restart


applies the provided attributes to the configurable items


Installs the cookbook based on the 'install_method'. Includes one of the following recipes


Downloads and installs the Zabbix agent from source


Sets up the Zabbix default repository and installs the agent from there


Downloads the Zabbix prebuilt tar.gz file and installs it


Needs testing


The LWRPs have been moved to the libzabbix cookbook.


To run the tests, insure you meet the below dependancies, then just run rake in the root of the cookbook


  • Verify and test on Windows
  • Verify and test on freebsd
  • Add cookbook_file install method



  • upgrade to default client version 3.0.9
  • move kitchen to docker so it can be run in travisci



  • include kitchen tests for all supported OS types
  • upgrade to default client version 2.4.4
  • cleanup source compile dependancies
  • added debian as supported
  • added more distributions and versions to kitchen testing
  • many bug fixes for diffrent distribution versions


  • Move LWRPs to their own cookbook to clean up zabbix-agent
  • Clean up linting and unit tests


  • Upgrading from 0.9.0 may require some slight changes to attribute names that control the configuration file.
  • Migrate zabbix_agentd.conf to a fully dynamically generated template
  • Include many more tests
  • General clean-up of code


  • Major refactor of all code.
  • Rename cookbook to zabbix-agent, strip out all server, web, java-gateway dependencies.
  • Add default code path chefspec tests
  • Update kitchen tests
  • Added package install from
  • Rename many cookbooks to follow a Install->Configure->Service design pattern.

0.8.0 forked from see this page for historical change log

Collaborator Number Metric

0.14.0 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric

0.14.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Foodcritic Metric

0.14.0 failed this metric

FC066: Ensure chef_version is set in metadata: zabbix-agent/metadata.rb:1
FC069: Ensure standardized license defined in metadata: zabbix-agent/metadata.rb:1
Run with Foodcritic Version 12.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric

0.14.0 passed this metric

No Binaries Metric

0.14.0 failed this metric

Failure: Cookbook should not contain binaries. Found:

Publish Metric

0.14.0 passed this metric

Supported Platforms Metric

0.14.0 passed this metric

Testing File Metric

0.14.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Version Tag Metric

0.14.0 passed this metric