[newrelic] ; ; Setting: newrelic.enabled ; Type : boolean ; Scope : per-directory ; Default: true ; Info : Enable or disable the agent. Please note that you cannot globally ; disable the agent and then selectively enable it on a per-directory ; basis. If you disable the agent in the global INI file then the ; agent will not initialize at all. However, you can selectively ; disable the agent on a per-directory basis. ; ;newrelic.enabled=true ; ; Setting: newrelic.daemon.max_threads ; Type : integer ; Scope : system ; Default: 8 ; Info : Sets the number of threads in the daemon "worker pool" that will be ; used for processing requests from each agent. The minimum is 4 and ; the maximum is 128. ; ;newrelic.daemon.max_threads = 8 ; ; Setting: newrelic.daemon.ssl ; Type : boolean ; Scope : system ; Default: true (as of version 3.6) ; Info : Sets whether or not communication with New Relic data collectors ; should use a secure HTTP connection or not. ; ;newrelic.daemon.ssl = true ; ; Setting: newrelic.daemon.proxy ; Type : string ; Scope : system ; Default: none ; Info : Sets the host and user credentials to use as an egress proxy. This ; is only used if your site requires a proxy in order to access ; external servers on the internet, in this case the New Relic data ; collection servers. This is expressed in one of the following forms: ; hostname ; hostname:port ; user@hostname ; user@hostname:port ; user:password@hostname ; user:password@hostname:port ; ;newrelic.daemon.proxy = "" ; ; Setting: newrelic.daemon.collector_host ; Type : string ; Scope : system ; Default: collector.newrelic.com ; Info : Sets the host name of the New Relic data collector host to use. ; Please note that this is NOT any form of local host. It refers to ; the New Relic provided host. There is very little reason to ever ; change this from the default except in certain very special ; circumstances, and then only on instruction from a New Relic sales ; person or support staff member. ; ;newrelic.daemon.collector_host = "collector.newrelic.com" ; ; Setting: newrelic.capture_params ; Type : boolean ; Scope : per-directory ; Default: false ; Info : Enable or disable the capturing of URL parameters. If enabled, then ; any variables passed on the URL like (for example ?id=12345) will be ; saved with the request and visible in various places in the web UI. ; If you tend to pass sensitive information around directly in the URL ; then its a good idea to keep this disabled. However, if your URL ; parameters are simply used for parameters without sensitive data but ; that are meaningful to each transaction then you can enable this. ; ;newrelic.capture_params = false ; Setting: newrelic.ignored_params ; Type : string ; Scope : per-directory ; Default: none ; Info : A comma-separated list of parameters to always exclude if parameter ; capturing is enabled above. You can use this to filter out sensitive ; user data that may appear as a URL parameter. ; ;newrelic.ignored_params = "" ; ; Setting: newrelic.error_collector.enabled ; Type : boolean ; Scope : per-directory ; Default: true ; Info : Enable the New Relic error collector. This will record the 20 most ; severe errors per harvest cycle. It is rare to want to disable this. ; Please also note that your New Relic subscription level may force ; this to be disabled regardless of any value you set for it. ; ;newrelic.error_collector.enabled = true ; ; Setting: newrelic.error_collector.record_database_errors ; Type : boolean ; Scope : per-directory ; Default: false ; Info : Currently only supported for MySQL database functions. If enabled, ; this will cause errors returned by various MySQL functions to be ; treated as if they were PHP errors, and thus subject to error ; collection. This is only obeyed if the error collector is enabled ; above and the account subscription level permits error trapping. ; ;newrelic.error_collector.record_database_errors = false ; ; Setting: newrelic.error_collector.prioritize_api_errors ; Type : boolean ; Scope : per-directory ; Default: false ; Info : If the error collector is enabled and you use the New Relic API to ; notice an error, if this is set to true then assign the highest ; priority to such errors. ; ;newrelic.error_collector.prioritize_api_errors = false ; ; Setting: newrelic.browser_monitoring.auto_instrument ; Type : boolean ; Scope : per-directory ; Default: true ; Info : Enables or disables automatic real user monitoring ("auto-RUM"). ; When enabled will cause the agent to insert a header and a footer ; in HTML output that will time the actual end-user experience. ; ;newrelic.browser_monitoring.auto_instrument = true ; ; Setting: newrelic.transaction_tracer.enabled ; Type : boolean ; Scope : per-directory ; Default: true ; Info : Enables or disables the transaction tracer. When enabled this will ; produce a detailed call graph for any transaction that exceeds a ; certain threshold (see next entry). Only one transaction trace per ; application per harvest cycle is stored and it is always the slowest ; transaction during that cycle. Transaction traces are extremely ; useful when diagnosing problem spots in your application. Please ; note that TT's may be disabled by your account subscription level ; regardless of what you set here. ; ;newrelic.transaction_tracer.enabled = true ; ; Setting: newrelic.transaction_tracer.threshold ; Type : string with a time specification or the word "apdex_f" ; Scope : per-directory ; Default: "apdex_f" ; Info : Specifies the threshold above which a transaction becomes a ; candidate for the transaction tracer. This can either be an absolute ; time value like "200ms" or "1s250ms" or "1h30m" or "750us" or the ; word "apdex_f". This last value, "apdex_f", means "4 times apdex_t". ; Thus the threshold changes according to your apdex_t setting. This ; is the default. ; ;newrelic.transaction_tracer.threshold = "apdex_f" ; ; Setting: newrelic.transaction_tracer.detail ; Type : integer in the range 0-2 ; Scope : per-directory ; Default: 1 ; Info : Sets the level of detail in a transaction trace. Setting this to 0 ; will only show the relatively few PHP functions that New Relic has ; deemed to be "interesting", as well as any custom functions you set ; (see below). A setting of 1 will trace and time all user functions, ; and a setting of 2, which needs another special variable to be set ; in order to take effect, will trace ALL PHP functions, including ; internal ones implemented in modules. This last setting can have a ; severe impact on performance which is why you need to consult New ; Relic support staff (create a case at https://one.newrelic.com/help-xp) to get the "special" ; variable to set to enable the feature. It is very rarely needed. ; ; In earlier releases of the agent this was known as "top100". ; ;newrelic.transaction_tracer.detail = 1 ; ; Setting: newrelic.transaction_tracer.slow_sql ; Type : boolean ; Scope : per-directory ; Default: true ; Info : Enables or disables the "slow SQL" tracer. When enabled, this will ; record the top 10 slowest SQL calls along with a stack trace of ; where the call occurred in your code. ; ;newrelic.transaction_tracer.slow_sql = true ; ; Setting: newrelic.transaction_tracer.stack_trace_threshold ; Type : time specification string ("500ms", "1s750ms" etc) ; Scope : per-directory ; Default: 500ms ; Info : Sets the threshold above which the New Relic agent will record a ; stack trace for a transaction trace. ; ;newrelic.transaction_tracer.stack_trace_threshold = 500 ; ; Setting: newrelic.transaction_tracer.explain_enabled ; Type : boolean ; Scope : per-directory ; Default: true ; Info : Enables or disables requesting "explain plans" from MySQL and ; PostgreSQL databases for slow SQL calls. The threshold for ; requesting explain plans is defined below. ; ;newrelic.transaction_tracer.explain_enabled = true ; ; Setting: newrelic.transaction_tracer.explain_threshold ; Type : time specification string ("750ms", "1s 500ms" etc) ; Scope : per-directory ; Default: 500ms ; Info : Used by the slow SQL tracer to set the threshold above which an SQL ; statement is considered "slow", and to set the threshold above which ; the transaction tracer will request an "explain plan" from the data- ; base for slow SQL. This latter feature may not be active yet, please ; refer to the agent release notes to see when it becomes available. ; Only relevant if explain_enabled above is set to true. ; ;newrelic.transaction_tracer.explain_threshold = 500 ; ; Setting: newrelic.transaction_tracer.record_sql ; Type : "off", "raw" or "obfuscated" ; Scope : per-directory ; Default: "obfuscated" ; Info : Sets how SQL statements are recorded (if at all). If this is set to ; "raw" then no attempt is made at obfuscating SQL statements. THIS IS ; HIGHLY DISCOURAGED IN PRODUCTION ENVIRONMENTS! Setting this to raw ; has considerable security implications as it can expose sensitive ; and private customer data. ; ;newrelic.transaction_tracer.record_sql = "obfuscated" ; Setting: newrelic.transaction_tracer.custom ; Type : string ; Scope : per-directory ; Default: none ; Info : Sets the name(s) of additional functions you want to instrument and ; appear in transaction traces. This is only meaningful if you have ; set newrelic.transaction_tracer.detail to 0. This can be a comma- ; separated list of function or class method names. ; ;newrelic.transaction_tracer.custom = "" ; ; Setting: newrelic.framework ; Type : string ; Scope : per-directory ; Default: empty (auto-detect framework) ; Info : Forces the framework to be one of the supported frameworks. This ; should only ever be used if the auto-detection fails, in which case ; the support team would very much like to know about the ; detection failure. Must be one of the following values: ; cakephp, codeigniter, drupal, joomla, kohana, magento, mediawiki, ; symfony, wordpress, yii, zend or no_framework. ; ;newrelic.framework = "" ; ; Setting: newrelic.webtransaction.name.remove_trailing_path ; Type : boolean ; Scope : per-directory ; Default: false ; Info : Used to aid naming transactions correctly when an unsupported ; framework is being used. This option will cause anything after the ; script name to be stripped from a URL. For example, setting this ; would cause the "/xyz/zy" to be stripped from a URL such as ; "/path/to/foo.php/xyz/zy". ; ;newrelic.webtransaction.name.remove_trailing_path = false ; ; Setting: newrelic.webtransaction.name.functions ; Type : string ; Scope : per-directory ; Default: none ; Info : Unless a specific framework such as Drupal or Wordpress has been ; detected, transactions are named according to the first script ; encountered, such as login.php. However, if you use a dispatcher ; file such as index.php this produces less useful data. If you use ; a dispatcher to redirect to actions such as "login", "show", "edit" ; etc, you can set this to the top level functions for those actions, ; and the function names specified here will be used to name the ; transaction. ; ;newrelic.webtransaction.name.functions = "" ; ; Setting: newrelic.webtransaction.name.files ; Type : string ; Scope : per-directory ; Default: none ; Info : Same as newrelic.webtransaction.name.functions above but using file ; names instead of function names. Accepts standard POSIX regular ; expressions. ; ;newrelic.webtransaction.name.files = "" ; ; Setting: newrelic.analytics_events.enabled ; Type : boolean ; Scope : per-directory ; Default: true ; info : Collect and report analytics event data. Event data allows the ; New Relic UI to show additional information such as histograms at ; the cost of additional daemon memory and collector communication. ; ;newrelic.analytics_events.enabled = true