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


newrelic-install (11) Versions 0.1.3

Installs/Configures Newrelic agents using guided install through chef

cookbook 'newrelic-install', '= 0.1.3', :supermarket
cookbook 'newrelic-install', '= 0.1.3'
knife supermarket install newrelic-install
knife supermarket download newrelic-install
Quality 33%

New Relic Experimental header

newrelic-install cookbook for Guided Install

newrelic-install is a chef cookbook created using on newrlic cli, and is currently in experimental phase.

Currently, we have included Linux and Windows support for New Relic's infrastructure and logs integrations.




  • Amazon Linux all versions
  • CentOS version 5 or higher
  • Debian version 7 ("Wheezy") or higher
  • Red Hat Enterprise Linux (RHEL) version 5 or higher
  • Ubuntu versions 16.04., 18.04., 20.04* (LTS versions)
  • Windows Server 2008, 2012, 2016, and 2019, and their service packs.
  • SUSE Linux Enterprise 11, 12


  • Chef 15+



Determines the platform and includes the appropriate platform specific recipe.
This is the only recipe that should be included in a node's run list.


Cookbook usage

  • Set any attributes necessary for your desired configuration
  • Add the newrelic-install::default recipe your run list

Resource usage

The newrelic_install resource manages will instrument newrelic using guided install with minimal configuration.

newrelic_install 'install' do
  action                   :install
  new_relic_api_key        node['newrelic_install']['env']['NEW_RELIC_API_KEY']
  new_relic_account_id     node['newrelic_install']['env']['NEW_RELIC_ACCOUNT_ID']
  env                      node['newrelic_install']['env']



Name Default value Description
default['newrelic_install']['env']['NEW_RELIC_API_KEY'] nil new relic api key
default['newrelic_install']['env']['NEW_RELIC_ACCOUNT_ID'] nil new relic account id


Name Default value Description
default['newrelic_install']['env']['NEW_RELIC_REGION'] US new relic region
default['newrelic_install']['env']['HTTP_PROXY'] nil proxy url if you are behind a firewall
default['newrelic_install']['verbosity'] nil Verbosity options for the installation (debug or trace). Writes verbose output to a log file on the host.
default['newrelic_install']['install_names'] %w(infrastructure-agent-installer log-integration) agents to be installed
default['newrelic_install']['tags'] {} key value pair tags added through custom attributes
default['newrelic_install']['timeout_seconds'] 600 Sets timeout for installation task.


Refer to testing

Releasing new versions

For releasing a new version to the Chef Supermarket follow this steps:

  • Update the version number in metadata.rb.
  • Create the github release for the new version.
  • Watch the build with the version number in Github Actions
  • If that passes, the new version should be on TBD


At New Relic we take your privacy and the security of your information
seriously, and are committed to protecting your information. We must emphasize
the importance of not sharing personal data in public forums,
and ask all users to scrub logs and diagnostic information for sensitive
information, whether personal, proprietary, or otherwise.

We define “Personal Data” as any information relating to an identified or
identifiable individual, including, for example, your name, phone number,
post code or zip code, Device ID, IP address, and email address.

For more information, review New Relic’s General Data Privacy Notice.


We encourage your contributions to improve this project! Keep in mind that
when you submit your pull request, you'll need to sign the CLA via the
click-through using CLA-Assistant. You only have to sign the CLA
one time per project.

If you have any questions, or to execute our corporate CLA (which is required
if your contribution is on behalf of a company),
drop us an email at

A note about vulnerabilities

As noted in our [security policy](../../security/policy), New Relic is
committed to the privacy and security of our customers and their data.
We believe that providing coordinated disclosure by security researchers
and engaging with the security community are important means to achieve our
security goals.

If you believe you have found a security vulnerability in this project or any
of New Relic's products or websites, we welcome and greatly appreciate you
reporting it to New Relic through HackerOne.

If you would like to contribute to this project, review [these guidelines](./

To all contributors, we thank you! Without your contribution, this project
would not be what it is today.


chef-install is licensed under the Apache 2.0

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

chef-install CHANGELOG

This file is used to list changes made in each version of the chef-install cookbook.


Initial release.

  • change 0
  • change 1

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, and your repo must contain a file

Cookstyle Metric

0.1.3 passed this metric

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, and your repo must contain a 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, and your repo must include a tag that matches this cookbook version number