- Setup - The basics of getting started with newrelic
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- 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.
newrelic::os: 'os': key: 'insert key'
newrelic::os: 'os': key: 'insert key' labels: - 'os:linux' - 'environment:dev'
Labels can also be done as a string if there is only one.
newrelic::os: 'os': key: 'insert key' labels: 'os:linux'
newrelic::java: 'java': key: 'insert key' app_root: '/tmp' version: '3.27.0' app_name: 'fred'
Then you are in luck. The global key variable will take car of that.
newrelic::global_key: 'insert key'
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
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
This will cause the module to fail.
This is the root of the application that is going to be monitored by Newrelic.
Source of the java agent. Default is
The type of java agent. Default is
This is used by node.js to identify the application. Default is
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.