PHP agent configuration

Configuration file variables

During installation, the newrelic-install script provides information about the configuration files it created or a list of files you need to edit. By default it will attempt to create a configuration file named newrelic.ini.

In some cases, you may be instructed to add configuration options to your php.ini file. Only do this if necessary. Exactly which file you need to edit depends on how your particular version (or versions) of PHP were configured.

The two most common configurations are:

• Use a single newrelic.ini file. This is usually the default if you have installed or compiled PHP yourself with no special options.
• Scan a given directory for all .ini files.

If you are unsure which file to edit:

• From the command line, review the output of php -i.

• In a browser, review the output of a page containing the script:

  <?php phpinfo(); ?>

• If the newrelic.ini file appears, use it.

Variable scope

Each variable for your newrelic.ini file has a defined scope. The scope controls where the setting can be established or modified.

The two scopes supported for New Relic settings are:

• SYSTEM: Values set globally in the global newrelic.ini file.
• PERDIR: Values set on a per-directory basis.

Each can also be set at a more general level. Valid locations for each are:

Variable type

Each variable for your newrelic.ini file has a defined type. The type specifies the syntax for the value you use.

General configuration settings

These settings are available in the newrelic.ini file.

newrelic.appname (HIGHLY RECOMMENDED)

Scope:	PERDIR
Type:	String (use quotes)
Default:	"PHP Application"

This config option sets the application name that data is reported under in New Relic APM. New Relic highly recommends that you replace the default name with a descriptive name to avoid confusion and unintended aggregation of data. Data for all applications with the same name will be merged in the New Relic UI, so set this carefully.

For all application-naming options, including per-directory settings, see Name your PHP application.

The setting's value is a semicolon-separated list of up to three application names. The first name in the list is the primary application name. It must be unique for each account. The application name is used as a key into a cache. When using multiple names for an app, New Relic only uses the first name for caching. Therefore, each application name can only appear as the first element once.

Caching example

If you set newrelic.appname="App1;App2" and later in the code set newrelic.appname="App1;App3", the second one will appear not to work. It will report to App1 and App2 because of the caching.

If you need overlapping application names, set the common application name in the second or third positions. For example: newrelic.appname="App2;App1" and newrelic.appname="App3;App1". This is useful, for example, when you want to track a superset of applications.

newrelic.capture_params

Scope:	PERDIR
Type:	Boolean
Default:	false

This setting has been deprecated and may not behave as expected. Instead, use attribute properties.

To set this value programmatically, use the newrelic_capture_params() API function.

If you pass sensitive information directly in the URL, keep this disabled.

If set to true, this will enable the recording of parameters passed to a PHP script via the URL (everything after the ? in the URL) in transaction traces. These will appear under the Parameters dropdown when displaying transaction traces.

newrelic.framework

Scope:	PERDIR
Type:	String (use quotes)
Default:	(auto-detected)

The New Relic PHP agent automatically detects the frameworks it supports, but problems may arise if you are using experimental new versions or if you have customized the framework. This setting disables automatic framework detection, instead telling the agent to attempt to name transactions according to the specified framework.

Specifying "no_framework" will disable framework-related transaction naming entirely.

Use any of the following values, as appropriate:

• "cakephp"
• "codeigniter"
• "drupal" (for Drupal 6 and 7)
• "drupal8"
• "joomla"
• "kohana"
• "laravel"
• "magento"
• "magento2"
• "mediawiki"
• "silex"
• "symfony1"
• "symfony2" (for Symfony 2 and 3)
• "wordpress"
• "yii"
• "zend"
• "zend2" (for Zend Framework 2 and 3)
• "no_framework" (to force no framework even if one was detected)

If the framework auto-detection fails, this command will also fail.

newrelic.ignored_params

Scope:	PERDIR
Type:	String (use quotes)
Default:	""

Use the newrelic.ignored_params setting to specify a comma-separated list of parameter names to be excluded from the list of parameters sent to the New Relic servers. Enclose the string values with quote marks.

If you enable parameter capturing with newrelic.capture_params, there may be parameters with sensitive user data you do not want to be captured by New Relic or visible in transaction traces. Use this to block the recording of this data.

newrelic.license (REQUIRED)

Scope:	PERDIR
Type:	String (use quotes)
Default:	""
Notes:	Introduced in agent version 3.0.

Sets the New Relic license key to use. In a multi-tenant system this can be set on a per-directory basis.

When you upgrade from an old agent version to 3.0 or higher, the license will be removed from your daemon configuration file (with a comment explaining why) and stored in the file /etc/newrelic/upgrade_please.key. Copy the license out of that file and set it in your newrelic.ini file. Delete the upgrade_please.key file.

newrelic.loglevel

Scope:	SYSTEM
Type:	String (use quotes)
Default:	"info"

Sets the level of detail of messages sent to the log file. Possible values, in increasing order of detail, include:

• error
• warning
• info
• verbose
• debug
• verbosedebug

When reporting any agent issues to New Relic technical support, verbosedebug is the most useful setting. However, this can generate a lot of information very quickly, so avoid keeping the agent at verbosedebug level for longer than it takes to reproduce the problem you are experiencing.

When reporting any agent issues to New Relic Technical Support, you may be asked to set this to a custom level, enabling debugging only for certain subsystems. Custom levels are beyond the scope of this document.

newrelic.transaction_tracer.detail

Scope:	PERDIR
Type:	Number
Default:	1
Notes:	This used to be newrelic.transaction_tracer.top100.

Sets the level of detail in a transaction trace:

• When set to 1, all server calls are traced.
• When set to 0, traces only include internally instrumented calls by New Relic and those defined by the user using newrelic.transaction_tracer.custom.

The default level of 1 does have a performance impact. If you need to improve performance, try setting the detail level to 0.

When not tracing all server calls, blocks of time in transaction traces will be labeled as uninstrumented time, and only certain functions (defined internally by the agent) are instrumented. Even when reporting all calls, there may be uninstrumented time in the traces.

newrelic.high_security

Scope:	SYSTEM
Type:	Boolean
Default:	false

Enables high security for all applications. When high security is set to true, the following behaviors take effect:

• Data will not be sent to New Relic unless the newrelic-daemon is using a secure connection (HTTPS). If the PHP process spawns a newrelic-daemon, it will be configured to use HTTPS regardless of the value of newrelic.daemon.ssl.
• Raw query strings will never be gathered, regardless of the value of newrelic.transaction_tracer.record_sql.
• Request attributes will never be captured, regardless of the newrelic.attributes configuration settings.
• The newrelic_add_custom_parameter and newrelic_set_user_attributes API function will have no effect, and they will return false.
• The newrelic_record_custom_event API function will not submit any events to New Relic Insights.
• The agent strips exception messages from errors.

If you change the newrelic.high_security setting, you must also change the security setting in the New Relic APM user interface. If the two settings do not match, then no data will be collected. For more information, see High security.

newrelic.labels

Scope:	PERDIR
Type:	String (use quotes)
Default:	""

Sets the label names and values to associate with the application. The list is a semi-colon delimited list of colon-separated name and value pairs.

Example labels

"Server:One;Data Center:Primary"

newrelic.process_host.display_name

Scope:	SYSTEM
Type:	String (use quotes)
Default:	""

Sets the hostname to be displayed in the APM UI. If set, this overrides the default hostname that the agent captures automatically.

Daemon .ini settings

The values of these settings control the daemon startup. When the agent detects that the daemon needs to be started, it will convert these options into the appropriate command line options for the daemon.

All of these settings mirror the settings in the newrelic.cfg file. They are repeated here to keep all of the .ini settings in one place. Each setting in newrelic.cfg has its counterpart here, with newrelic.daemon. as the prefix. For example, the ssl setting in newrelic.cfg is newrelic.daemon.ssl in an .ini file.

For more information about ways to start the daemon and when to use an external configuration file, see PHP daemon startup modes.

newrelic.daemon.app_timeout

Scope:	SYSTEM
Type:	Time specification string; for example, "5m" or "1h20m"
Default:	"10m"

Sets the elapsed time after which an application will be considered inactive. Inactive applications do not count against the maximum limit of 250 applications. Allowed units are "ns", "us", "ms", "s", "m", and "h".

A value of 0 will be interpreted as "no timeout." This will result in new applications always counting towards the 250 application limit, as well as the daemon being unable to release a small amount of memory per application back to the operating system.

Recommendation: Do not use this value unless New Relic Support requests it. Instead, for occasional background transactions, use a value of twice the interval. For example, for an hourly background job, set the timeout to 2 hours.

newrelic.daemon.auditlog

Scope:	SYSTEM
Type:	String (use quotes)
Default:	""

The setting specifies the name of an audit log, which will contain all of the data sent from the daemon to the New Relic servers, including the full URL, date, time, and the uncompressed, unencoded data for each request.

This file cannot be the same file as the daemon log.

This audit log can become very large, very quickly. Avoid using the newrelic.daemon.auditlog setting for extended periods of time. Its primary purpose is to allow system administrators to perform security reviews and to observe exactly what data transmits.

newrelic.daemon.collector_host

Scope:	SYSTEM
Type:	String (use quotes)
Default:	"collector.newrelic.com"

Sets the name and optional port of the collector host which the daemon will contact to verify your license key and send agent data.

This is either just the name of the host or the name and port number in the form "hostname:port". Specifying a port number of 0 will use the default port, which is 80.

Do not change this value unless New Relic Support instructs you.

newrelic.daemon.dont_launch

Scope:	SYSTEM
Type:	Number
Default:	0

If you prefer to have the daemon launched externally before the agent starts up, this value determines when the agent is allowed to start the daemon:

• 0: No restrictions are placed on daemon startup and the agent can start the daemon any time.
• 1: Non-command line (such as Apache or php-fpm) agents can start the daemon.
• 2: Only command line agents can start the daemon.
• 3: The agent will never start the daemon. Use this setting if you are configuring the daemon via newrelic.cfg and starting it outside of the agent.

If /etc/newrelic/newrelic.cfg exists, the agent assumes the daemon is meant to be started by its startup script, not via the agent. This setting has no meaning to and does not appear in newrelic.cfg.

newrelic.daemon.location

Scope:	SYSTEM
Type:	String (use quotes)
Default:	"/usr/bin/newrelic-daemon"

Sets the name of the daemon executable to launch.

This variable identifies the full path to the daemon executable file. If the New Relic system was installed using the standard packages, the default location will be correct. If you have installed to a custom location using the tar distribution (and do not have permission to write to /usr/bin), then the daemon may reside at another location.

This setting does not appear in the newrelic.cfg file as it is only relevant to PHP.

On OpenSolaris, /usr is frequently a read-only file system. The default daemon location for OpenSolaris is /opt/newrelic/bin/newrelic-daemon.

newrelic.daemon.logfile

Scope:	SYSTEM
Type:	String (use quotes)
Default:	"/var/log/newrelic/newrelic-daemon.log"

Sets the name of the log file to record daemon specific log messages. This file must be writable by the daemon. The most common case is that the Apache user will end up starting the daemon when Apache itself starts up, thus you should ensure that the file is writable by whichever user runs the Apache process.

You can use write permissions to this file as a means of restricting who can start the daemon.

newrelic.daemon.loglevel

Scope:	SYSTEM
Type:	String (use quotes)
Default:	"info"

Sets the detail level for messages recorded to New Relic's daemon log file. Possible values, in increasing order of detail, are:

• error
• warning
• info
• debug

The more verbose settings can generate a lot of information very quickly. When necessary, set debug for short periods of time to identify problems.

newrelic.daemon.pidfile

Scope:	SYSTEM
Type:	String (use quotes)
Default:	(depends on OS)

Sets the name of the file in which the daemon will record its process ID (pid).

This file is used by the daemon startup and shutdown script to determine whether or not the daemon is already running.

newrelic.daemon.port

Scope:	SYSTEM
Type:	String or Number
Default:	"/tmp/.newrelic.sock"

Sets the socket endpoint for agent to daemon communications.

This can be specified in three ways.

• To use a specified file as a UNIX domain socket (UDS), provide an absolute path name as a string. This is the preferred mechanism.
• To use a standard TCP port, specify a number in the range 1 to 65534.
• To use an abstract socket, use the value @newrelic-daemon (available for agent version 5.2.0.141 and higher).

If you use port numbers, Unix systems require that ports in the range 1 to 1023 require the daemon be run as the super-user. In case the daemon uses a non-standard port, this variable also sets the port number the agent will use for communicating with the daemon.

If you are using the newrelic.cfg startup mechanism for the daemon then this setting and the port setting in that file must match.

newrelic.daemon.proxy

Scope:	SYSTEM
Type:	String (use quotes)
Default:	""

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 the New Relic data collection servers. It can take any of the following forms, depending on the proxy setup:

• hostname
• hostname:port
• user@hostname
• user@hostname:port
• user:password@hostname
• user:password@hostname:port
• proxytype://user:password@hostname:port

A proxy type of HTTP is assumed unless another proxytype is specified. In that case, proxytype can be one of http, socks4, socks4a, or socks5.

newrelic.daemon.ssl

Scope:	SYSTEM
Type:	Boolean
Default:	true

This setting is ignored on PHP agent versions 8.0 and higher, and HTTPS will always be used to communicate with New Relic.

On versions of the PHP agent versions lower than 8.0, controls whether or not communication with New Relic collectors should use a secure HTTP connection. The agent communicates with New Relic via HTTPS by default, and New Relic requires HTTPS for all traffic to New Relic APM and the New Relic REST API.

newrelic.daemon.ssl_ca_bundle

Scope:	SYSTEM
Type:	String (use quotes)
Default:	""

Sets the location of a file containing CA certificates in PEM format. When set, the certificates in this file will be used to authenticate the New Relic collector. In most cases it should not be necessary to configure a CA bundle. The New Relic PHP agent comes bundled with the necessary CA certificates.

If newrelic.daemon.ssl_ca_path is also set, the certificates in this file will be searched first, followed by the certificates contained in the newrelic.daemon.ssl_ca_path directory.

This setting has no effect when newrelic.daemon.ssl is set to false.

newrelic.daemon.ssl_ca_path

Scope:	SYSTEM
Type:	String (use quotes)
Default:	""

Sets the location of a directory containing trusted CA certificates in PEM format. When set, the certificates in this directory will be used to authenticate the New Relic collector. In most cases it should not be necessary to configure a CA path. The New Relic PHP agent comes bundled with the necessary CA certificates.

If newrelic.daemon.ssl_ca_bundle is also set, it will be searched first followed by the certificates contained in newrelic.daemon.ssl_ca_path.

This setting has no effect when newrelic.daemon.ssl is set to false.

Transaction tracer .ini settings

The values of these settings are used to control transaction traces.

newrelic.transaction_tracer.custom

Scope:	PERDIR
Type:	String (use quotes)
Default:	""

Set this to a comma-separated list of user defined functions or methods to instrument:

"myfunction,myclass::method,otherfunction"

Internal PHP functions cannot have custom tracing.

You can add to the list of custom functions with each PERDIR file, but you cannot remove a function or method that has already been added. If you want to programmatically add functions or methods to be instrumented, use the newrelic_add_custom_tracer() API function call.

newrelic.transaction_tracer.enabled

Scope:	PERDIR
Type:	Boolean
Default:	true

Enables or disables the transaction tracer.

The tracer creates a detailed transaction trace for transactions that take more time than the threshold, as set by the newrelic.transaction_tracer.threshold value. Only one transaction trace per application per harvest cycle is stored and it is always the slowest transaction during that cycle.

Transaction traces are useful for diagnosing why a particular transaction was slow. Unless memory and performance are critical, they should almost never be disabled. Enabling this does have a very slight performance impact and does use more memory.

For more information, see newrelic.transaction_tracer.detail.

newrelic.transaction_tracer.explain_enabled

Scope:	PERDIR
Type:	Boolean
Default:	true

Enables or disables requesting explain plans from MySQLi and PDO MySQL libraries for slow query calls. Explain plans will only be available when newrelic.transaction_tracer.slow_sql is set to true and newrelic.transaction_tracer.record_sql is not set to "off".

newrelic.transaction_tracer.explain_threshold

Scope:	PERDIR
Type:	Duration
Default:	"500"

Sets the threshold beyond which queries are considered "slow" and thus candidates for the Slow Queries page. Specify duration as an absolute value with units. Default unit is in milliseconds if none is specified.

Example durations

• "200ms"
• "1s250ms"
• "1h30m"
• "750us"

newrelic.transaction_tracer.internal_functions_enabled

Scope:	SYSTEM
Type:	Boolean
Default:	false

Enables or disables support for tracing internal functions (that is, functions written in C and provided either via the PHP standard library or PECL extensions). When enabled, internal functions appear in transaction traces like functions written in PHP.

Enabling this option may result in transactions being slower, especially when collecting many traces from PHP 5.x. Enabling this option is only recommended when specifically debugging performance issues where an internal function is suspected to be slow.

newrelic.transaction_tracer.record_sql

Scope:	PERDIR
Type:	String (use quotes)
Default:	"obfuscated"

Sets how queries are recorded (if at all).

When recording transaction traces internally, the full query for slow query calls is recorded. Sending this query to New Relic can have serious security implications, so by default, all database statements are obfuscated before being sent to New Relic. The obfuscation is not reversible, as it replaces strings and numbers in any query with question marks. The only things that survive intact are field names, not any of their values.

• If you are testing with data that is not sensitive and you need to see the raw queries in transaction traces, set this to "raw".
• If you do not want queries recorded at all, set this to "off".

Always set this back to "obfuscated" or "off" in any production environment.

newrelic.transaction_tracer.slow_sql

Scope:	PERDIR
Type:	Boolean
Default:	true

Use this setting to enable or disable the Slow Queries feature. When enabled, it will:

• Record the top 10 slowest database queries per application per minute.
• Create a stack trace leading up to the query.

If this variable is set to false or SQL recording is disabled, the New Relic agent does not gather any slow query data.

newrelic.transaction_tracer.stack_trace_threshold

Scope:	PERDIR
Type:	Duration
Default:	"500"

This sets the threshold above which the agent will record the full PHP stack for transaction traces for which queries are being recorded.

Specify duration as an absolute value with units. Default unit is in milliseconds if none is specified.

Example durations

• "200ms"
• "1s250ms"
• "1h30m"
• "750us"

Stack traces can consume memory, so be careful of setting this value too low. This variable has no meaning if newrelic.transaction_tracer.record_sql is set to "off".

newrelic.transaction_tracer.threshold

Scope:	PERDIR
Type:	Duration
Default:	"apdex_f"

Use this variable to set the threshold beyond which transactions are eligible for being traced. Available values include:

• Use "apdex_f" to set the threshold to 4 times the application's apdex_t value. For more information, see Apdex: Measuring user satisfaction.
• Use any other duration string to set a specific time threshold. Specify the duration as an absolute value and the unit of measurement. If none is specified, the unit defaults to millisecond.

Example durations

• "200ms"
• "1s250ms"
• "1h30m"
• "750us"

newrelic.transaction_tracer.gather_input_queries

Scope:	PERDIR
Type:	Boolean
Default:	true

Use this setting to enable or disable gathering of DQL input queries with Slow Queries and Transaction Traces. When enabled, these will appear along with slow queries and transaction traces.

Other tracer .ini settings

The values of these settings are used to control various tracer features.

newrelic.cross_application_tracer.enabled

A distributed tracing feature is available. Distributed tracing improves on cross application tracing and is recommended for monitoring activity in complex distributed systems.

Scope:	PERDIR
Type:	Boolean
Default:	true

Enable or disable the cross application tracer. The cross application tracer inserts HTTP headers into outbound requests and the response in order to link together web transaction metrics and transaction traces between applications.

Distributed tracing and cross application tracing cannot be used simultaneously. The default configuration for the PHP agent disables distributed tracing and enables cross application tracing.

newrelic.distributed_tracing_enabled

Scope:	PERDIR
Type:	Boolean
Default:	false

Enabling distributed tracing disables cross-application tracing. Before enabling, read the transition guide to understand effects on New Relic features.

Enable or disable distributed tracing. When the agent's transaction tracer and distributed tracing features are enabled, the agent will insert headers into outbound requests, and scan incoming requests for distributed tracing headers.

newrelic.transaction_tracer.enabled = true
newrelic.distributed_tracing_enabled = true

newrelic.span_events_enabled

Scope:	PERDIR
Type:	Boolean
Default:	true

Span events are reported for distributed tracing. Span event reporting requires distributed tracing to be enabled. This option enables/disables the reporting of span events.

newrelic.error_collector.enabled

Scope:	PERDIR
Type:	Boolean
Default:	true

Enable or disable the error collector. When enabled, the agent collects and reports PHP errors to the New Relic UI.

The agent records only the single most severe error for each transaction, and up to 20 errors per harvest cycle.

For an overview of error configuration in New Relic APM, see Manage errors in APM.

newrelic.error_collector.record_database_errors

Scope:	PERDIR
Type:	Boolean
Default:	true

When enabled, the agent collects errors returned by MySQL functions as if they were PHP errors.

newrelic.error_collector.prioritize_api_errors

Scope:	PERDIR
Type:	Boolean
Default:	false

Set this to true to assign the highest priority to errors identified through the newrelic_notice_error() API function.

newrelic.error_collector.ignore_exceptions

Scope:	PERDIR
Type:	String
Default:	(none)

A comma separated list of fully-qualified exception class names that the agent should ignore. When an unhandled exception occurs, the agent will perform the equivalent of $exception instanceof Class for each of the classes listed. If any of those checks returns true, the agent will not record an exception.

Depending on the supported PHP release, these values are equivalent to disabling exception reporting:

• Supported PHP 5 versions: newrelic.error_collector.ignore_exceptions = Exceptions
• Supported PHP 7 versions: newrelic.error_collector.ignore_exceptions = Throwable

newrelic.error_collector.ignore_errors

Scope:	PERDIR
Type:	Integer or a bitwise expression of PHP-defined error constants
Default:	0

Sets the error levels for the PHP agent to ignore. The value for this setting uses similar syntax to PHP's error_reporting option. For example, to configure the PHP agent to ignore E_WARNING and E_ERROR level errors, use:

newrelic.error_collector.ignore_errors = E_WARNING | E_ERROR

or

newrelic.error_collector.ignore_errors = 3

To configure the PHP agent to ignore everything but E_WARNING, use:

newrelic.error_collector.ignore_errors = E_ALL & ~E_WARNING

newrelic.framework.drupal.modules

Scope:	PERDIR
Type:	Boolean
Default:	true
Notes:	In agents prior to version 3.0 the default for this value was false. Setting this option implied newrelic.transaction_tracer.detail = 1.

To enable Drupal module tracking, set this to true. This option has the same performance impact as newrelic.transaction_tracer.detail. It will enable the recording of Drupal module functions and call counts, and they will display under the Modules tab, much like web transactions.

newrelic.framework.wordpress.hooks

Scope:	PERDIR
Type:	Boolean
Default:	true

To enable WordPress hook tracking, set this to true. It will enable the recording of WordPress hooks, plugins, and themes, and they will display under the WordPress tab in the New Relic UI.

newrelic.webtransaction.name.files

Scope:	PERDIR
Type:	String (use quotes)
Default:	""

This is the same as newrelic.webtransaction.name.functions, except it uses file names to name the web transaction. The file names can be standard POSIX regular expression to be used with PCRE; for example, "controllers/actions/.*".

newrelic.webtransaction.name.functions

Scope:	PERDIR
Type:	String (use quotes)
Default:	""

Unless the New Relic agent detects a specific framework, such as Drupal or Wordpress, web transactions are named after the initial PHP file; for example, article.php.

When the initial file is a dispatcher, this naming scheme produces less than useful data. Use this variable to specify a list of functions that are the "actions" generated by the dispatcher. The name of the web transaction will be the first action function executed.

Example dispatch function naming

If index.php dispatches to functions named:

• login,
• logout,
• admin,
• show, and
• edit

You would set this value to "login,logout,admin,show,edit".

The web transactions will be named login, logout, etc. instead of /index.php (the initial file name).

newrelic.webtransaction.name.remove_trailing_path

Scope:	PERDIR
Type:	Boolean
Default:	false

When enabled,this removes any content in the request URI after the script name. For example, this would remove the trailing /xyz/zy from /path/to/foo.php/xyz/zy.

newrelic.datastore_tracer.instance_reporting.enabled

Scope:	PERDIR
Type:	Boolean
Default:	true

If false, the agent will not report datastore instance metrics, nor add host or port_path_or_id parameters to transaction or slow sql traces.

newrelic.datastore_tracer.database_name_reporting.enabled

Scope:	PERDIR
Type:	Boolean
Default:	true

If false, the agent will not add database_name parameter to transaction or slow sql traces.

Attribute settings

This section lists the settings that affect attribute collection and reporting.

newrelic.attributes.enabled

Scope:	PERDIR
Type:	Boolean
Default:	true

Enable or disable the collection of attributes generated by the PHP agent or generated by the user through newrelic_add_custom_parameter(). This setting will take precedence over all other attribute configuration settings.

For more information, see Enabling and disabling attributes.

newrelic.{destination}.attributes.enabled

Scope:	PERDIR
Type:	Boolean
Default:	True, except for browser_monitoring.attributes.enabled

Control which destinations receive attributes. These configuration settings will override the .include and .exclude settings.

For more information on the destinations available, see Enabling and disabling attributes.

newrelic.attributes.{include|exclude}

Scope:	PERDIR
Type:	String
Default:	(none)

This is a family of configuration options that allow fine control over the destinations of attributes. For more information, see Enabling and disabling attributes.

For more help