| @@ -0,0 +1,221 @@ |
| | 1 | # This file configures the New Relic Agent. New Relic monitors |
| | 2 | # Ruby, Java, .NET, PHP, and Python applications with deep visibility and low overhead. |
| | 3 | # For more information, visit www.newrelic.com. |
| | 4 | |
| | 5 | # Here are the settings that are common to all environments |
| | 6 | common: &default_settings |
| | 7 | # ============================== LICENSE KEY =============================== |
| | 8 | |
| | 9 | # You must specify the license key associated with your New Relic |
| | 10 | # account. This key binds your Agent's data to your account in the |
| | 11 | # New Relic service. |
| | 12 | license_key: '<%= ENV["NEW_RELIC_LICENSE_KEY"] %>' |
| | 13 | |
| | 14 | # Agent Enabled (Ruby/Rails Only) |
| | 15 | # Use this setting to force the agent to run or not run. |
| | 16 | # Default is 'auto' which means the agent will install and run only |
| | 17 | # if a valid dispatcher such as Mongrel is running. This prevents |
| | 18 | # it from running with Rake or the console. Set to false to |
| | 19 | # completely turn the agent off regardless of the other settings. |
| | 20 | # Valid values are true, false and auto. |
| | 21 | # |
| | 22 | # agent_enabled: auto |
| | 23 | |
| | 24 | # Application Name Set this to be the name of your application as |
| | 25 | # you'd like it show up in New Relic. The service will then auto-map |
| | 26 | # instances of your application into an "application" on your |
| | 27 | # dashboard page. If you want to map this instance into multiple |
| | 28 | # apps, like "AJAX Requests" and "All UI" then specify a semicolon |
| | 29 | # separated list of up to three distinct names, or a yaml list. |
| | 30 | # Defaults to the capitalized RAILS_ENV or RACK_ENV (i.e., |
| | 31 | # Production, Staging, etc) |
| | 32 | # |
| | 33 | # Example: |
| | 34 | # |
| | 35 | # app_name: |
| | 36 | # - Ajax Service |
| | 37 | # - All Services |
| | 38 | # |
| | 39 | app_name: '<%= ENV["NEW_RELIC_APP_NAME"] %>' |
| | 40 | |
| | 41 | # When "true", the agent collects performance data about your |
| | 42 | # application and reports this data to the New Relic service at |
| | 43 | # newrelic.com. This global switch is normally overridden for each |
| | 44 | # environment below. (formerly called 'enabled') |
| | 45 | monitor_mode: true |
| | 46 | |
| | 47 | # Developer mode should be off in every environment but |
| | 48 | # development as it has very high overhead in memory. |
| | 49 | developer_mode: false |
| | 50 | |
| | 51 | # The newrelic agent generates its own log file to keep its logging |
| | 52 | # information separate from that of your application. Specify its |
| | 53 | # log level here. |
| | 54 | log_level: info |
| | 55 | |
| | 56 | # Optionally set the path to the log file This is expanded from the |
| | 57 | # root directory (may be relative or absolute, e.g. 'log/' or |
| | 58 | # '/var/log/') The agent will attempt to create this directory if it |
| | 59 | # does not exist. |
| | 60 | # log_file_path: 'log' |
| | 61 | |
| | 62 | # Optionally set the name of the log file, defaults to 'newrelic_agent.log' |
| | 63 | # log_file_name: 'newrelic_agent.log' |
| | 64 | |
| | 65 | # The newrelic agent communicates with the service via https by default. This |
| | 66 | # prevents eavesdropping on the performance metrics transmitted by the agent. |
| | 67 | # The encryption required by SSL introduces a nominal amount of CPU overhead, |
| | 68 | # which is performed asynchronously in a background thread. If you'd prefer |
| | 69 | # to send your metrics over http uncomment the following line. |
| | 70 | # ssl: false |
| | 71 | |
| | 72 | #============================== Browser Monitoring =============================== |
| | 73 | # New Relic Real User Monitoring gives you insight into the performance real users are |
| | 74 | # experiencing with your website. This is accomplished by measuring the time it takes for |
| | 75 | # your users' browsers to download and render your web pages by injecting a small amount |
| | 76 | # of JavaScript code into the header and footer of each page. |
| | 77 | browser_monitoring: |
| | 78 | # By default the agent automatically injects the monitoring JavaScript |
| | 79 | # into web pages. Set this attribute to false to turn off this behavior. |
| | 80 | auto_instrument: false |
| | 81 | |
| | 82 | # Proxy settings for connecting to the New Relic server. |
| | 83 | # |
| | 84 | # If a proxy is used, the host setting is required. Other settings |
| | 85 | # are optional. Default port is 8080. |
| | 86 | # |
| | 87 | # proxy_host: hostname |
| | 88 | # proxy_port: 8080 |
| | 89 | # proxy_user: |
| | 90 | # proxy_pass: |
| | 91 | |
| | 92 | # The agent can optionally log all data it sends to New Relic servers to a |
| | 93 | # separate log file for human inspection and auditing purposes. To enable this |
| | 94 | # feature, change 'enabled' below to true. |
| | 95 | # See: https://newrelic.com/docs/ruby/audit-log |
| | 96 | audit_log: |
| | 97 | enabled: false |
| | 98 | |
| | 99 | # Tells transaction tracer and error collector (when enabled) |
| | 100 | # whether or not to capture HTTP params. When true, frameworks can |
| | 101 | # exclude HTTP parameters from being captured. |
| | 102 | # Rails: the RoR filter_parameter_logging excludes parameters |
| | 103 | # Java: create a config setting called "ignored_params" and set it to |
| | 104 | # a comma separated list of HTTP parameter names. |
| | 105 | # ex: ignored_params: credit_card, ssn, password |
| | 106 | capture_params: false |
| | 107 | |
| | 108 | # Transaction tracer captures deep information about slow |
| | 109 | # transactions and sends this to the New Relic service once a |
| | 110 | # minute. Included in the transaction is the exact call sequence of |
| | 111 | # the transactions including any SQL statements issued. |
| | 112 | transaction_tracer: |
| | 113 | |
| | 114 | # Transaction tracer is enabled by default. Set this to false to |
| | 115 | # turn it off. This feature is only available at the Professional |
| | 116 | # and above product levels. |
| | 117 | enabled: false |
| | 118 | |
| | 119 | # Threshold in seconds for when to collect a transaction |
| | 120 | # trace. When the response time of a controller action exceeds |
| | 121 | # this threshold, a transaction trace will be recorded and sent to |
| | 122 | # New Relic. Valid values are any float value, or (default) "apdex_f", |
| | 123 | # which will use the threshold for an dissatisfying Apdex |
| | 124 | # controller action - four times the Apdex T value. |
| | 125 | transaction_threshold: apdex_f |
| | 126 | |
| | 127 | # When transaction tracer is on, SQL statements can optionally be |
| | 128 | # recorded. The recorder has three modes, "off" which sends no |
| | 129 | # SQL, "raw" which sends the SQL statement in its original form, |
| | 130 | # and "obfuscated", which strips out numeric and string literals. |
| | 131 | record_sql: obfuscated |
| | 132 | |
| | 133 | # Threshold in seconds for when to collect stack trace for a SQL |
| | 134 | # call. In other words, when SQL statements exceed this threshold, |
| | 135 | # then capture and send to New Relic the current stack trace. This is |
| | 136 | # helpful for pinpointing where long SQL calls originate from. |
| | 137 | stack_trace_threshold: 0.500 |
| | 138 | |
| | 139 | # Determines whether the agent will capture query plans for slow |
| | 140 | # SQL queries. Only supported in mysql and postgres. Should be |
| | 141 | # set to false when using other adapters. |
| | 142 | # explain_enabled: true |
| | 143 | |
| | 144 | # Threshold for query execution time below which query plans will |
| | 145 | # not be captured. Relevant only when `explain_enabled` is true. |
| | 146 | # explain_threshold: 0.5 |
| | 147 | |
| | 148 | # Error collector captures information about uncaught exceptions and |
| | 149 | # sends them to New Relic for viewing |
| | 150 | error_collector: |
| | 151 | |
| | 152 | # Error collector is enabled by default. Set this to false to turn |
| | 153 | # it off. This feature is only available at the Professional and above |
| | 154 | # product levels. |
| | 155 | enabled: true |
| | 156 | |
| | 157 | # Rails Only - tells error collector whether or not to capture a |
| | 158 | # source snippet around the place of the error when errors are View |
| | 159 | # related. |
| | 160 | capture_source: true |
| | 161 | |
| | 162 | # To stop specific errors from reporting to New Relic, set this property |
| | 163 | # to comma-separated values. Default is to ignore routing errors, |
| | 164 | # which are how 404's get triggered. |
| | 165 | ignore_errors: "ActionController::RoutingError,Sinatra::NotFound" |
| | 166 | |
| | 167 | # If you're interested in capturing memcache keys as though they |
| | 168 | # were SQL uncomment this flag. Note that this does increase |
| | 169 | # overhead slightly on every memcached call, and can have security |
| | 170 | # implications if your memcached keys are sensitive |
| | 171 | # capture_memcache_keys: true |
| | 172 | |
| | 173 | # Application Environments |
| | 174 | # ------------------------------------------ |
| | 175 | # Environment-specific settings are in this section. |
| | 176 | # For Rails applications, RAILS_ENV is used to determine the environment. |
| | 177 | # For Java applications, pass -Dnewrelic.environment <environment> to set |
| | 178 | # the environment. |
| | 179 | |
| | 180 | # NOTE if your application has other named environments, you should |
| | 181 | # provide newrelic configuration settings for these environments here. |
| | 182 | |
| | 183 | development: |
| | 184 | <<: *default_settings |
| | 185 | # Turn off communication to New Relic service in development mode (also |
| | 186 | # 'enabled'). |
| | 187 | # NOTE: for initial evaluation purposes, you may want to temporarily |
| | 188 | # turn the agent on in development mode. |
| | 189 | monitor_mode: false |
| | 190 | |
| | 191 | # Rails Only - when running in Developer Mode, the New Relic Agent will |
| | 192 | # present performance information on the last 100 transactions you have |
| | 193 | # executed since starting the mongrel. |
| | 194 | # NOTE: There is substantial overhead when running in developer mode. |
| | 195 | # Do not use for production or load testing. |
| | 196 | developer_mode: true |
| | 197 | |
| | 198 | # Enable textmate links |
| | 199 | # textmate: true |
| | 200 | |
| | 201 | test: |
| | 202 | <<: *default_settings |
| | 203 | # It almost never makes sense to turn on the agent when running |
| | 204 | # unit, functional or integration tests or the like. |
| | 205 | monitor_mode: false |
| | 206 | |
| | 207 | # Turn on the agent in production for 24x7 monitoring. NewRelic |
| | 208 | # testing shows an average performance impact of < 5 ms per |
| | 209 | # transaction, you can leave this on all the time without |
| | 210 | # incurring any user-visible performance degradation. |
| | 211 | production: |
| | 212 | <<: *default_settings |
| | 213 | monitor_mode: true |
| | 214 | |
| | 215 | # Many applications have a staging environment which behaves |
| | 216 | # identically to production. Support for that environment is provided |
| | 217 | # here. By default, the staging environment has the agent turned on. |
| | 218 | staging: |
| | 219 | <<: *default_settings |
| | 220 | monitor_mode: true |
| | 221 | # app_name: My Application (Staging) |