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


packetbeat (12) Versions 1.0.0

Installs/Configures Elastic Packetbeat

cookbook 'packetbeat', '~> 1.0.0', :supermarket
cookbook 'packetbeat', '~> 1.0.0'
knife supermarket install packetbeat
knife supermarket download packetbeat
Quality 17%

packetbeat Cookbook

CookbookBuild Status

This is a Chef cookbook to manage PacketBeat.

For Production environment, always prefer the most recent release.

Most Recent Release

cookbook 'packetbeat', '~> 1.0.0'

From Git

cookbook 'packetbeat', github: 'vkhatri/chef-packetbeat',  tag: 'v1.0.0'


Supported OS

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


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

  • packetbeat::install - install packetbeat

  • packetbeat::config - configure packetbeat

How to Add Packetbeat Output via Node Attribute

ElasticSearch Output

  "default_attributes": {
    "packetbeat": {
      "config": {
        "output": {
          "elasticsearch": {
            "enabled": true,
            "hosts": [""],
            "save_topology": false,
            "max_retries": 3,
            "bulk_max_size": 1000,
            "flush_interval": null,
            "protocol": "http",
            "username": null,
            "password": null,
            "index": "packetbeat",
            "path": "/elasticsearch"

Logstash Output

  "default_attributes": {
    "packetbeat": {
      "config": {
        "output": {
          "logstash": {
            "enabled": true,
            "hosts": [""],
            "loadbalance": true,
            "save_topology": false,
            "index": "packetbeat"

File Output

  "default_attributes": {
    "packetbeat": {
      "config": {
        "output": {
          "file": {
            "enabled": true,
            "path": "/tmp/packetbeat",
            "filename": "packetbeat",
            "rotate_every_kb": 1000,
            "number_of_files": 7

Core Attributes

  • default['packetbeat']['version'] (default: 5.6.4): packetbeat version

  • default['packetbeat']['packages'] (default: calculated): package dependencies

  • default['packetbeat']['conf_dir'] (default: /etc/packetbeat): packetbeat yaml configuration file directory

  • default['packetbeat']['conf_file'] (default: /etc/packetbeat/packetbeat.yml): packetbeat configuration file

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

  • default['packetbeat']['disable_service'] (default: false): whether to stop and disable packetbeat service

Configuration File packetbeat.yml Attributes

  • default['packetbeat']['config']['device'] (default: any): packetbeat interface device name

  • default['packetbeat']['config']['protocols'] (default: {}): packetbeat services to capture packets

  • default['packetbeat']['config']['output'] (default: {}): packetbeat output configuration attributes

For more attribute info, visit below links:


  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

elastic_beats_repo >= 0.0.0
yum-plugin-versionlock >= 0.1.2

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

packetbeat CHANGELOG

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


  • Virender Khatri - updated beats to v5.6.4

  • Virender Khatri - added preview release support

  • Virender Khatri - updated kitchen dokken test

  • Virender Khatri - optional elastic beats repo setup

  • Virender Khatri - conditional service restart

  • Virender Khatri - package version lock

  • Virender Khatri - use cookbook elastic_beats_repo

  • Virender Khatri - added amazon platform support


  • Virender Khatri - enabled ci kitchen tests

  • Virender Khatri - updated beats to v5.2.2


  • Virender Khatri - updated beats to v5.1.2


  • Virender Khatri - added beatx v5.x support

  • Virender Khatri - updated beats to v5.1.1


  • Virender Khatri - updated beats to v1.3.1

  • Virender Khatri - update travis ruby version

  • Virender Khatri - updated kitchen os


  • Virender Khatri - update to beats v1.2.3

  • Virender Khatri - added deb package option and apt distribution


  • Virender Khatri - #23, add yum_repository resource attribute metadata_expiry

  • Virender Khatri - #22, update to beats v1.0.1

  • Virender Khatri - #20, add output configuration example


  • Virender Khatri - #18, major changes to support repository package install

  • Virender Khatri - #19, fix kitchen test


  • Virender Khatri - #9, disable default['packetbeat']['config']['output']['elasticsearch']['hosts']

  • Virender Khatri - #10, ignore service restart on config change on disable_service

  • Virender Khatri - #11, remove dumy file packetbeat.yml

  • Jose Alberto - bump Packetbeat verion to 1.0.0 rc2

  • Jose Alberto - adapt attributes to new breaking changes

  • Jose Alberto - change defaults no more outputs by default

  • Virender Khatri - #14, update package_url to auto

  • Virender Khatri - #15, ubuntu packetbeat.yml package file conflict issue during upgrade

  • Virender Khatri -#16, added spec

  • Virender Khatri - #17, added 32bit platform support


  • Virender Khatri - #8, optional attribute to stop and disable the service

  • Virender Khatri - #7, update version to beta3

  • Virender Khatri - #6, update default attriutes for new protocol support in beta3 release


  • Virender Khatri - issue #5, bump packetbeat version to 1.0.0-beta2

  • Virender Khatri - issue #4, separate attributes file for config

  • Virender Khatri - issue #3, notify packetbeat service on config change

  • Virender Khatri - issue #2, default[packetbeat][notify_restart] default value must be true

  • Virender Khatri - issue #1, save_topology default value set to true

  • Virender Khatri - added more default config parameters info to config attribute file

  • Virender Khatri - fixed typo and updated README


  • Virender Khatri - Initial release of packetbeat

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

1.0.0 failed this metric

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

Contributing File Metric

1.0.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

1.0.0 failed this metric

FC109: Use platform-specific package resources instead of provider property: packetbeat/recipes/install_preview.rb:29
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric

1.0.0 passed this metric

Testing File Metric

1.0.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

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