Forge Home


Installs newrelic


7,107 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.3.0 (latest)
  • 0.2.3
  • 0.2.2
  • 0.2.1
  • 0.2.0
  • 0.1.0
released Sep 9th 2016
This version is compatible with:
  • , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'Firebladee-newrelic', '0.3.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add Firebladee-newrelic
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install Firebladee-newrelic --version 0.3.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



Firebladee/newrelic — version 0.3.0 Sep 9th 2016

Build Status


Table of Contents

  1. Description
  2. Setup - The basics of getting started with newrelic
  3. Usage - Configuration options and additional functionality
  4. Reference - An under-the-hood peek at what the module is doing and how
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module


This module is to add the newrelic agent's to your machine/application. What can this modulle setup.

  • os
  • node.js
  • php
  • java


I want to monitor the os.

For hiera

    key: 'insert key'

I need to add labels.

    key: 'insert key'
      - 'os:linux'
      - 'environment:dev'

Labels can also be done as a string if there is only one.

    key: 'insert key'
    labels: 'os:linux'

I need to monitor a java app.

    key: 'insert key'
    app_root: '/tmp'
    version: '3.27.0'
    app_name: 'fred'

I am feed up repeating my key.

Then you are in luck. The global key variable will take car of that.

newrelic::global_key: 'insert key'

I need the new relic repo installed.

newrelic::repo_install: true



This is used as the global key for the hash's. Saves having to type the key in for each hash.


This will add the repo to allow the newrelic packages to be installed. Default value: false


This is used to install or remove the agent. Default is present.


This is the key for your newrelic account. If left blank then the agent will be setup but nothing will be sent to the newrelic web site.


Used to specify the version of java plugin you want. Defaults to undef. This will cause the module to fail.


This is the root of the application that is going to be monitored by Newrelic. Default is undef.


Source of the java agent. Default is


The type of java agent. Default is agent.


This is used by node.js to identify the application. Default is undef.


For the Redhat family, this has been tested on Centos. So we have a baisc assumption that this will work on Redhat.


Just the standard, i.e. fork, make change add rspec/beaker tests and then push request. If you are not ofay with rspec and beaker then still make the push request and we will help you with that.