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

Select Status


topbeat (6) Versions 0.1.7

Installs/Configures Elastic Topbeat

cookbook 'topbeat', '~> 0.1.7', :supermarket
cookbook 'topbeat', '~> 0.1.7'
knife supermarket install topbeat
knife supermarket download topbeat
Quality 17%

topbeat Cookbook

CookbookBuild Status

This is a Chef cookbook to manage Topbeat.

For Production environment, always prefer the most recent release.

Most Recent Release

cookbook 'topbeat', '~> 0.1.7'

From Git

cookbook 'topbeat', github: 'vkhatri/chef-topbeat'


Supported OS

This cookbook was tested on Amazon & Ubuntu Linux and expected to work on other RHEL platforms and Windows.


  • topbeat::default - default recipe (use it for run_list)

  • topbeat::install - install topbeat for rhel, debian, ubuntu based OS

  • topbeat::config - configure topbeat

  • topbeat::install_windows - configure topbeat for windows based OS

Core Attributes

  • default['topbeat']['version'] (default: 1.3.1): topbeat version

  • default['topbeat']['release'] (default: 1): topbeat release for yum package

  • default['topbeat']['packages'] (default: []): package dependencies

  • default['topbeat']['conf_dir'] (default: /etc/topbeat or C:/opt/topbeat/topbeat-1.2.1-windows/): topbeat yaml configuration file directory

  • default['topbeat']['conf_file'] (default: /etc/topbeat/topbeat.yml or C:/opt/topbeat/topbeat-1.2.1-windows/topbeat.yml): topbeat configuration file

  • default['topbeat']['notify_restart'] (default: true): whether to restart topbeat service on configuration file change

  • default['topbeat']['disable_service'] (default: false): whether to stop and disable topbeat service, useful for maintenance mode

Configuration File topbeat.yml Attributes

  • default['topbeat']['config']['input']['period'] (default: 10): topbeat statistics collection interval

  • default['topbeat']['config']['input']['period'] (default: 10): topbeat procs to collect statistics

  • default['topbeat']['config']['output'] (default: {}): topbeat output configuration, e.g. elasticsearch, logstash, file etc.

For more attribute info, visit below link:

Topbeat YUM/APT Repository Attributes

  • default['topbeat']['yum']['description'] (default: ``): beats yum reporitory attribute

  • default['topbeat']['yum']['gpgcheck'] (default: true): beats yum reporitory attribute

  • default['topbeat']['yum']['enabled'] (default: true): beats yum reporitory attribute

  • default['topbeat']['yum']['baseurl'] (default:$basearch): beatsyum reporitory attribute

  • default['topbeat']['yum']['gpgkey'] (default: beats yum reporitory attribute

  • default['topbeat']['yum']['action'] (default: :create): beats yum reporitory attribute

  • default['topbeat']['apt']['description'] (default: calculated): beats apt reporitory attribute

  • default['topbeat']['apt']['components'] (default: ['stable', 'main']): beats apt reporitory attribute

  • default['topbeat']['apt']['uri'] (default: beats apt reporitory attribute

  • default['topbeat']['apt']['key'] (default: beats apt reporitory attribute

  • default['topbeat']['apt']['action'] (default: :add): filebeat apt reporitory attribute


  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  3. Write your change
  4. Write tests for your change (if applicable)
  5. Run the tests (rake & rake knife), ensuring they all pass
  6. Write new resource/attribute description to
  7. Write description about changes to PR
  8. Submit a Pull Request using Github

Authors:: Virender Khatri and Contributors

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

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

Dependent cookbooks

yum >= 0.0.0
apt >= 0.0.0
windows >= 0.0.0
yum-plugin-versionlock >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.


This file is used to list changes made in each version of the topbeat cookbook.


  • Virender Khatri - #19, include yum-plugin-versionlock only for rhel

  • Virender Khatri - updated kitchen spec

  • Virender Khatri - updated beats version to 1.3.1

  • Virender Khatri - restart topbeat service on package upgrade


  • Virender Khatri - fix for #18, failed to install pinned version on version change


  • Paul Morton - support version pinning in deb and yum repos

  • Virender Khatri - updated travis to use ruby v2.2.2

  • Virender Khatri - remove powershell cookbook dependency

  • Virender Khatri - updated topbeat version to v1.3.0

  • Virender Khatri - use cookbook yum-plugin-versionlock instead


  • Bob - adding support for windows

  • Bob - add serverpec integration tests for all platforms

  • Virender Khatri - bump beats version to v1.2.3


  • Virender Khatri - Fixed README typo


  • Jose Alberto - bump version to 1.0.0-rc2 adn new defult config

  • Virender Khatri - #3, added travis ci

  • Virender Khatri - #5, update package download url to auto

  • Virender Khatri - #8, fix kitchen test

  • Virender Khatri - #4, added specs

  • Virender Khatri - #9, added source url. issue url, platforms metadata

  • Virender Khatri - #7, added repository package install


  • Virender Khatri - Initial release of topbeat

Check the Markdown Syntax Guide for help with Markdown.

The Github Flavored Markdown page describes the differences between markdown on github and standard markdown.

Collaborator Number Metric

0.1.7 failed this metric

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

Contributing File Metric

0.1.7 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.1.7 failed this metric

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

No Binaries Metric

0.1.7 passed this metric

Testing File Metric

0.1.7 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.1.7 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 include a tag that matches this cookbook version number