Chef cookbook for the New Relic infrastructure agent

This cookbook installs and configures the New Relic infrastructure agent, as well New Relic and and on-host integrations.

Install and use the Chef cookbook

Requirements

Platforms

• 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

• Chef 15+

Recipes

newrelic-infra::default

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.

newrelic-infra::agent_linux

Installs and configures the Infrastructure agent on a Linux host. This recipe should NOT be directly included in a node's run list. The default recipe will automatically determine which platform specific recipe to apply.

Here are the steps that the recipe performs:

1. Adds the newrelic-infra package repository source.
2. Can install, upgrade, or remove the newrelic-infra package. By default, the package is only installed.
3. Enables and starts the newrelic_infra agent service.
4. Generates the agent configuration file.
5. Includes the newrelic-infra::host_integrations recipe to install and configure any on-host integrations.

newrelic-infra::agent_windows

Installs and configures the Infrastructure agent on a Windows host. This recipe should NOT be directly included in a node's run list. The default recipe will automatically determine which platform specific recipe to apply.

newrelic-infra::host_integrations

Installs New Relic provided and on-host integrations if the integration has been addded to the list of host_integrations (for example, default['newrelic_infra']['features]['host_integrations'] = []). It also generates configuration for any of the available on-host integrations from New Relic, and installs any custom integrations defined with attributes.

For more infromation on the available custom resource for installing and configuring custom on-host integrations see the [Custom resources][9] documentation.

Example configuration for a custom on-host integration installed and configured via attributes:

default['newrelic_infra']['custom_integrations']['test_integration'] = {
  integration_name: 'com.test.integration',
  remote_url: 'https://url-to-a-tarball-for-install.com/test.tar.gz',
  instances: [
    {
      name: 'test_integration_metrics',
      command: 'metrics',
      arguments: {
        test: true
      },
      labels: {
        environment: 'test'
      }
    }
  ],
  commands: {
    metrics: %w[--metrics]
  }
}

For more information on the available New Relic on-host integrations and configuration you can check the [official documentation][6].

Attributes

See attributes/defaults.rb for more details and default values.

APT repository attributes

The apt_repository Chef resource is built using metaprogramming, so that the configuration can be extended via attributes. Any property available to the resource can be passed in via attributes.

Attributes that cannot be passed to the resource are logged out as warnings in order to prevent potential failes from typos, older Chef versions, etc.
For more information, refer to the Chef documentation on the apt_repository resource.

Windows attributes

When using Windows, you can set a source URL and checksum for the agent download.

Yum repository attributes

The yum_repository Chef resource is built using metaprogramming, so that the configuration can be extended via attributes. Any property available to the resource can be passed in via attributes.

Attributes that cannot be passed to the resource are logged out as warnings in order to prevent potential failes from typos, older Chef versions, etc.
For more information, refer to the Chef documentation on the yum_repository resource.

Custom Resources

newrelic_infra_integration

Installs and configures a custom New Relic Infrastructure on-host integration.

Example:

newrelic_infra_integration 'test' do
  integration_name 'test_integration'
  remote_url 'https://url-to-a-tarball-for-install.com/test.tar.gz'
  commands { metrics: %w[--metrics] }
  instances(
    [
      {
        name: 'test_integration_metrics',
        command: 'metrics',
        arguments: {
          test: true
        },
        labels: {
          environment: 'test'
        }
      }
    ]
  )
end

Supported properties:

Usage

Cookbook usage

• Set any attributes necessary for your desired configuration
• Add the newrelic-infra::default recipe your run list
• For wrapper cookbooks, add the newrelic-infra cookbook as a dependency to your metadata.rb or Berksfile, then include newrelic-infra::default recipe.

Custom resource usage

• Add the newrelic-infra cookbook as a dependency to your metadata.rb or Berksfile
• Configure the custom resource(s) using the supported properties

Testing

Refer to
https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD

Releasing new versions

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

• Update the version number in [metadata.rb][13].
• Create the github release for the new version. This will trigger a GitHub Actions job that will deploy the new version.
• Watch the build with the version number in Github Actions: https://github.com/newrelic/infrastructure-agent-chef/actions
• If that passes, the new version should be on https://supermarket.chef.io/cookbooks/newrelic-infra and available to use everywhere

Support

Should you need assistance with New Relic products, you are in good hands with several support diagnostic tools and support channels.

New Relic offers NRDiag, a client-side diagnostic utility that automatically detects common problems with New Relic agents. If NRDiag detects a problem, it suggests troubleshooting steps. NRDiag can also automatically attach troubleshooting data to a New Relic Support ticket. Remove this section if it doesn't apply.

If the issue has been confirmed as a bug or is a feature request, file a GitHub issue.

Support Channels

• New Relic Documentation: Comprehensive guidance for using our platform
• New Relic Community: The best place to engage in troubleshooting questions
• New Relic Developer: Resources for building a custom observability applications
• New Relic University: A range of online training for New Relic users of every level
• New Relic Technical Support 24/7/365 ticketed support. Read more about our Technical Support Offerings.

Privacy

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.

Contribute

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 opensource@newrelic.com.

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](./CONTRIBUTING.md).

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

License

infrastructure-agent-chef is licensed under the Apache 2.0 License.