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


spartan_loggly_rsyslog (6) Versions 2.1.2

Configures rsyslog to send logs to Loggly

cookbook 'spartan_loggly_rsyslog', '= 2.1.2', :supermarket
cookbook 'spartan_loggly_rsyslog', '= 2.1.2'
knife supermarket install spartan_loggly_rsyslog
knife supermarket download spartan_loggly_rsyslog
Quality 100%

Loggly rsyslog Cookbook

Note: This has been forked from apetresc/loggly-rsyslog.

Installs and configures rsyslog for use with Loggly.


  • Chef 11 or higher
  • Ruby 1.9.3 or higher


Tested against Ubuntu 12.04

Data Bags

By default, this cookbook depends on the use of encrypted data bags to store the token to be used. For more information about data bags see the Chef Data Bags documentation. By default, the data bag needs to be named loggly and contains an item token:

    "id": "token",
    "token": ""

You may change the name of the data bag and item via the node['loggly']['token']['databag'] and node['loggly']['token']['databag_item'] attributes respectively.
Also, if you do not want this cookbook to load the credentials for you, and instead want to set them yourself, set node['loggly']['token']['from_databag'] to false, and then set the credentials via node['loggly']['token']['value'].


  • node['loggly']['tags'] - A list of event tags to apply to a message ( (optional)

  • node['loggly']['log_files'] - A list of files rsyslog should monitor. (optional). Below is an example
    of a hash used to describe a file to monitor.

        :filename => "/var/log/filename.log",
        :tag => "tag you want for this logfile",
        :statefile => "unique-name-for-statefile"

* `node['loggly']['log_dirs']` - A list of directories to monitor (optional). The loggly configuration template will create an [imfile]( block for each file ending in '.log' in that directory. Each logdir in the list is of the format:
        :directory => "/var/log/directory",
        :tag => "tag for all files in this directory"

* `node['loggly']['tls']['enabled']` - Set to true if communication to the remote service should use TLS (defaults to true)
* `node['loggly']['tls']['cert_path']` - Directory where the loggly certificate should be placed
* `node['loggly']['tls']['cert_url']` - Url to the certificate
* `node['loggly']['tls']['cert_checksum']` - Checksum of the certificate
* `node['loggly']['tls']['intermediate_cert_url']` - Url to the intermediate certificate
* `node['loggly']['tls']['intermediate_cert_checksum']` - Checksum of the intermediate certificate

* `default['loggly']['token']['from_databag']` - Whether to load the Loggly token from a Data Bag (defaults to true)
* `default['loggly']['token']['databag']` - The name of the Data Bag to load the credentials from (defaults to "loggly")
* `default['loggly']['token']['databag_item']` - The name of the Data Bag Item to load the credentials from (defaults to "token")
* `default['loggly']['token']['value']` - The Loggly token. Set from the Data Bag above by default.

* `node['loggly']['rsyslog']['conf']` - Name of the loggly rsyslog configuration file (defaults to /etc/rsyslog.d/10-loggly.conf)
* `node['loggly']['rsyslog']['host']` - Name of the remote loggly syslog host (defaults to
* `node['loggly']['rsyslog']['port']` - Port of the remote loggly syslog host (defaults to 514 and if TLS is enabled to 6514)
* `node['loggly']['rsyslog']['input_file_poll_interval']` - Specifies how often files are to be polled for new data (defaults to 10)

Include the default recipe in the run list or a cookbook. The cookbook includes the rsyslog cookbook that will install the rsyslog package and start the service if it does not exist. The rsyslog service will restart after changes to the loggly rsyslog configuration file are made.

Running Locally with Vagrant
Since the cookbook relies on using an encrypted data bag, there is some additional steps that are needed in order to run the cookbook locally using Vagrant. The create_data_bag.rb is a helper script that can be used to create the data bag for loggly for use with Vagrant and Chef Solo. The script expects a single argument, the value of the loggly token.

Add the following two lines into your Vagrantfile in the chef_solo provisioner configuration:

chef.data_bags_path = './data_bags'
chef.encrypted_data_bag_secret_key_path = './encrypted_data_bag_secret'

License & Authors

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

apt ~> 2.0
rsyslog ~> 1.13.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

spartan_loggly_rsyslog Cookbook CHANGELOG

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


  • Finish refactoring name to spartan_loggly_rsyslog.
  • Added an .editorconfig file.


  • Update fork of cookbook to be managed by Spartan.


  • Use an encrypted databag to retrieve the loggly token instead of a node attribute


  • Set rsyslog configuration values to be configurable via attributes

v1.0.0 (1/25/2014)

  • Initial cookbook version
  • Support for sending messages using TLS
  • Configuration for monitoring a list of files
  • Configuration for monitoring a list of directories

Foodcritic Metric

2.1.2 passed this metric