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

RSS

logentries (2) Versions 0.1.3

Installs and manages Logentries.

Policyfile
Berkshelf
Knife
cookbook 'logentries', '~> 0.1.3', :supermarket
cookbook 'logentries', '~> 0.1.3'
knife supermarket install logentries
knife supermarket download logentries
README
Dependencies
Quality 17%

chef-logentries

Description

Installs the Logentries Agent, and provides definitions to manage registering servers and following logs.

Requirements

Supported Platforms

The following platforms are supported by this cookbook, meaning that the recipes run on these platforms without error:

  • Ubuntu

Recipes

  • logentries - Set up the apt repository and install the logentries package

Usage

This cookbook installs the Logentries Agent package from the Logentries apt repository.

Additionally this cookbook provides a logentries definition which you can use to register hosts, follow logs, and execute other le based commands.

# register a server
logentries do
  account_key 'abcdefgh-ijkl-mnop-qrst-uvwxyz123456'
  server_name 'appserver'

  action :register
end

# follow a log (if it hasn't already been logged)
logentries '/var/log/syslog' do
  log_name 'Syslog'
  action :follow
end

You can use logentries from a json node config too by specifying a logentries element in your config with an account_key, server_name, and optionally some log_files.

{
  "logentries": {
    "account_key": "abcdefgh-ijkl-mnop-qrst-uvwxyz123456",
    "server_name": "My Server",
    "log_files": {
      "App Server": "/var/www/myapp/log/production.log",
      "Syslog": "/var/log/syslog"
    }
  }
}

Notes

Logentries is split into two packages, logentries and logentries-daemon, the former contains the command-line tools and the latter is the reporting agent. Unfortunately, when you install the logentries-daemon package it immediately tries to start the agent and will fail if you haven't pre-configured your host settings; this is problematic in a Chef script, because we haven't had an opportunity to set things up yet.

To solve this problem, the commandline tools are installed immediately, then the logentries-daemon package will only be installed at the end of your chef run; it will be triggered by the use of any of the logentries definitions.

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

License

chef-logentries

Dependent cookbooks

apt >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

0.1.3 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.3 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 https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

0.1.3 failed this metric

FC064: Ensure issues_url is set in metadata: logentries/metadata.rb:1
FC065: Ensure source_url is set in metadata: logentries/metadata.rb:1
FC066: Ensure chef_version is set in metadata: logentries/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.3 passed this metric

Testing File Metric
            

0.1.3 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 https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

0.1.3 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 https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number