.NET agent configuration

For .NET Framework, the following variables are required:

COR_ENABLE_PROFILING=1
COR_PROFILER={71DA0A04-7777-4EC6-9643-7D28B46A8A41}
NEWRELIC_INSTALL_PATH="INSERT_THE_PATH_TO_THE_AGENT_DIRECTORY"

The Windows .NET agent installer (.msi) will add these to IIS by default, or as system-wide environment variables when enabling Instrument All.

When using the Windows .NET agent installer, ensure that NEWRELIC_INSTALL_PATH is set to C:\Program Files\New Relic\.NET Agent\. This is where the agent DLLs are placed on the system.

For more details on these variables, as well as correct values for other installation scenarios, please see understanding .NET agent environment variables.

When installing the agent via the Nuget package, the agent requires a different set of environment variables.

For .NET Core, the following variables are required:

Linux:

CORECLR_ENABLE_PROFILING=1
CORECLR_PROFILER={36032161-FFC0-4B61-B559-F6C5D41BAE5A}
CORECLR_NEWRELIC_HOME=path/to/agent/directory
CORECLR_PROFILER_PATH="${CORECLR_NEWRELIC_HOME}/libNewRelicProfiler.so"

Windows (MSI Installer):

CORECLR_ENABLE_PROFILING=1
CORECLR_PROFILER={36032161-FFC0-4B61-B559-F6C5D41BAE5A}
NEWRELIC_INSTALL_PATH=C:\Program Files\New Relic\.NET Agent\
CORECLR_NEWRELIC_HOME=C:\ProgramData\New Relic\.NET Agent\

The Windows .NET agent installer will add these to IIS by default, or as system-wide environment variables when enabling Instrument All. Exception: CORECLR_ENABLE_PROFILING needs to be set manually in order to instrument non-IIS hosted .NET Core applications. See Compatibility and requirements for .NET Framework for .NET Framework applications.

For more details on these variables, as well as correct values for other installation scenarios, please see understanding .NET agent environment variables.

When installing the agent via the Nuget package in Windows, the agent requires a different set of environment variables.

New Relic's .NET agents rely on environment variables to tell the .NET Common Language Runtime (CLR) to load New Relic into your processes. The install-related environment variables are Microsoft variables, not New Relic variables. They can be used by other .NET profilers, and only one profiler can be attached to a process at a time. For this reason, if you have used previous application monitoring products, you may have profiler conflicts.

The 64-bit MSI installer for New Relic's .NET agent automatically installs the 32-bit profiler assembly along with the 64-bit assembly and as of v10.16.0, enables 32-bit support for IIS automatically. For non-IIS hosted applications, you can set the required environment variable manually.

COR_PROFILER_PATH_32="C:\Program Files (x86)\New Relic\.NET Agent\NewRelic.Profiler.dll"

Enable or disable the New Relic agent.

The maximum number of stack frames to trace in any stack dump.

Your New Relic license key. New Relic uses the license key to match your app's data to the correct account in the UI. Set the license key via environment variable.

Alternatively, set the NEW_RELIC_LICENSE_KEY environment variable in the application's environment:

NEW_RELIC_LICENSE_KEY=YOUR_LICENSE_KEY

Instructs the agent to record execution environment information. Environment information includes operating system, agent version, and which assemblies are available.

Block application startup until the agent connects to New Relic. If set to true, the first transaction may take substantially longer to complete, because it is blocked until the connection to New Relic is finished.

Block application shutdown while the agent initiates a final harvest cycle and sends all data to New Relic.

Alternatively, set the NEW_RELIC_SEND_DATA_ON_EXIT environment variable in the application's environment:

NEW_RELIC_SEND_DATA_ON_EXIT=true

The minimum amount of time the process must run before the agent blocks it from shutting down. This setting only applies when sendDataOnExit is true.

Alternatively, set the NEW_RELIC_SEND_DATA_ON_EXIT_THRESHOLD_MS environment variable in the application's environment:

NEW_RELIC_SEND_DATA_ON_EXIT_THRESHOLD_MS=2000

If false, the agent uses a pool thread to complete the transaction processing.

If true, the agent will complete transaction processing on the request thread.

If false, the agent attempts to re-use existing transactions when custom instrumented methods are encountered in async/threaded scenarios.

If true, the agent attempts to create new transactions when custom instrumented methods are encountered in async/threaded scenarios.

Alternatively, the NEW_RELIC_FORCE_NEW_TRANSACTION_ON_NEW_THREAD environment variable may be used to control this behavior.

NEW_RELIC_FORCE_NEW_TRANSACTION_ON_NEW_THREAD=true

The agent's request timeout when communicating with New Relic.

Automatically start the .NET agent when the first instrumented method is hit.

Provides the ability to configure a FedRAMP compliant endpoint for the agent to use, with the value gov-collector.newrelic.com.

<service licenseKey="YOUR_LICENSE_KEY"
  host="gov-collector.newrelic.com" />

You can also use the environment variable NEW_RELIC_HOST.

NEW_RELIC_HOST=gov-collector.newrelic.com

Defines the proxy host.

Alternatively, set the NEW_RELIC_PROXY_HOST environment variable in the application's environment.

Defines the proxy port.

Alternatively, set the NEW_RELIC_PROXY_PORT environment variable in the application's environment.

Optionally define a proxy URI path.

Alternatively, set the NEW_RELIC_PROXY_URI_PATH environment variable in the application's environment.

Optionally define a domain to use when authenticating with the proxy server.

Alternatively, set the NEW_RELIC_PROXY_DOMAIN environment variable in the application's environment.

Optionally define a user name for authentication.

Alternatively, set the NEW_RELIC_PROXY_USER environment variable in the application's environment.

Optionally define a password for authentication.

Alternatively, set the NEW_RELIC_PROXY_PASS environment variable in the application's environment.

For additional security, the .NET Agent supports the use of an obfuscated proxy password with the passwordObfuscated attribute. The obfuscated proxy password is generated using the following New Relic CLI command:

$
newrelic agent config obfuscate --key OBSCURING_KEY --value "PLAIN_TEXT_PROXY_PASSWORD"

Alternatively, set the NEW_RELIC_PROXY_PASS_OBFUSCATED environment variable in the application's environment.

Defines the level of detail recorded in the log file. Possible values, in increasing order of detail, are:

• off

• error

• warn

• info

• debug

• finest

• all

  Alternatively, set the NEWRELIC_LOG_LEVEL environment variable in the application's environment.

  Importante

  Increasing the log level will increase New Relic's performance impact.

Records all data sent to and received from New Relic in both an auditlog log file and the standard log file.

Send log messages to the console, in addition to the log file. Alternatively, set the NEW_RELIC_LOG_CONSOLE environment variable in the application's environment.

If disabled, no logging is attempted. Intended for read-only file systems. Alternatively, set the NEW_RELIC_LOG_ENABLED environment variable in the application's environment.

The directory to hold log files generated by the agent. If this is omitted, then a directory named Logs in the New Relic agent install area will be used by default.

Alternatively, set the NEWRELIC_LOG_DIRECTORY environment variable in the application's environment. You can also send your profiler logs to a custom directory, but you can only do that with the NEWRELIC_PROFILER_LOG_DIRECTORY environment variable in the application's environment:

NEWRELIC_LOG_DIRECTORY=path\to\a\directory
NEWRELIC_PROFILER_LOG_DIRECTORY=path\to\a\directory # not configurable via config file

Defines a name for the log file. If you do not define a fileName, the name is derived from the name of the monitored process.

Alternatively, set the NEW_RELIC_LOG environment variable in the application's environment:

NEW_RELIC_LOG=MyApp.log

Defines the agent log file rolling strategy. Possible values are:

• size (default): The log file rolls over when it reaches the size specified in maxLogFileSizeMB.

• day: The log file rolls over at midnight.

  Alternatively, set the NEW_RELIC_LOG_ROLLING_STRATEGY environment variable in the application's environment:

  NEW_RELIC_LOG_ROLLING_STRATEGY=day

  Copiar

  Supported in .NET agent v10.21.0 and higher.

Defines the number of agent log files to retain per instance of the agent, multiple apps running on the same host will each each create this many files. When the maximum number of log files is reached, the oldest log file is deleted. A value of 0 specifies that there is no maximum number of log files.

Alternatively, set the NEW_RELIC_LOG_MAX_FILES environment variable in the application's environment:

NEW_RELIC_LOG_MAX_FILES=2

Supported in .NET agent v10.21.0 and higher.

Defines the maximum size of the agent log file in megabytes before it rolls over. Valid only when logRollingStrategy is set to size. A value of 0 specifies that there is no maximum log file size.

Alternatively, set the NEW_RELIC_LOG_MAX_FILE_SIZE_MB environment variable in the application's environment:

NEW_RELIC_LOG_MAX_FILE_SIZE_MB=100

Supported in .NET agent v10.21.0 and higher.

The name of your .NET application is a child of the application element. New Relic will aggregate your data according to this name. For example, if you have two running applications named AppA and AppB, you will see two applications in the New Relic interface: AppA and AppB.

You can also assign up to three names to your app. The first name is the primary name. For example:

<application>
  <name>MY APPLICATION PRIMARY</name>
  <name>SECOND APP NAME</name>
  <name>THIRD APP NAME</name>
</application>

Alternatively, set the NEW_RELIC_APP_NAME environment variable in the application's environment:

NEW_RELIC_APP_NAME=Descriptive Name

For multiple names:

NEW_RELIC_APP_NAME="App Name, App Name 2, App Name 3"

Samplers collect information about memory and CPU consumption. Set this to true to disable sampling.

Alternatively, set the NEW_RELIC_DISABLE_SAMPLERS environment variable in the application's environment:

NEW_RELIC_DISABLE_SAMPLERS=true

Defines the HTTP method used when sending data to New Relic. Set this to true to enable using the PUT method when sending data. The POST method is used by default.

Set the displayName attribute in the processHost element in newrelic.config. The processHost element is a child of the configuration element.

<configuration . . . >
  <processHost displayName="CUSTOM_NAME" />
</configuration>

Set the NEW_RELIC_PROCESS_HOST_DISPLAY_NAME environment variable:

NEW_RELIC_PROCESS_HOST_DISPLAY_NAME="CUSTOM_NAME"

Determines whether the agent polls AWS metadata API.

Alternatively, this behavior can be controlled via the NEW_RELIC_UTILIZATION_DETECT_AWS environment variable:

NEW_RELIC_UTILIZATION_DETECT_AWS=false

Determines whether the agent polls Microsoft Azure metadata API.

Alternatively, this behavior can be controlled via the NEW_RELIC_UTILIZATION_DETECT_AZURE environment variable:

NEW_RELIC_UTILIZATION_DETECT_AZURE=false

Determines whether the agent polls GCP metadata API.

Alternatively, this behavior can be controlled via the NEW_RELIC_UTILIZATION_DETECT_GCP environment variable:

NEW_RELIC_UTILIZATION_DETECT_GCP=false

Determines whether the agent polls PCF information from environment variables.

Alternatively, this behavior can be controlled via the NEW_RELIC_UTILIZATION_DETECT_PCF environment variable:

NEW_RELIC_UTILIZATION_DETECT_PCF=false

Determines whether the agent reads Docker information from the file system.

Alternatively, this behavior can be controlled via the NEW_RELIC_UTILIZATION_DETECT_DOCKER environment variable:

NEW_RELIC_UTILIZATION_DETECT_DOCKER=false

Determines whether the agent polls Kubernetes information from environment variables.

Alternatively, this behavior can be controlled via the NEW_RELIC_UTILIZATION_DETECT_KUBERNETES environment variable:

NEW_RELIC_UTILIZATION_DETECT_KUBERNETES=false

Enable or disable attribute collection. When set to false in the primary attribute element, this setting overrides all attribute settings for individual destinations.

Alternatively, set the NEW_RELIC_ATTRIBUTES_ENABLED environment variable in the application's environment.

If attributes are enabled, the agent will collect all attribute keys specified in this list. To specify multiple attribute keys, specify each individually. You can also use a * wildcard character at the end of a key to match multiple attributes (for example, myApiKey.*). For more information, see Attribute rules.

Alternatively, set the NEW_RELIC_ATTRIBUTES_INCLUDE environment variable in the application's environment. This environment variable accepts a comma delimited list of attribute names.

If attributes are enabled, the agent will not collect attribute keys specified in this list. To specify multiple attribute keys, specify each individually. You can also use a * wildcard character at the end of a key to match multiple attributes (for example, myApiKey.*). For more information, see Attribute rules.

Alternatively, set the NEW_RELIC_ATTRIBUTES_EXCLUDE environment variable in the application's environment. This environment variable accepts a comma delimited list of attribute names.

Defines how the .NET agent will behave on a "global" level for application pools served via IIS. The .NET agent instruments all application pools by default. When true, application pools listed under applicationPool with an instrument attribute set to false will not be instrumented.

Essentially, when set to false, the application pool list acts as an allow list. When set to true, the application pool list acts as a deny list.

Defines instrumentation behavior for a specific application pool. The name attribute is the name of an application pool. Enable or disable profiling in the instrument attribute. Define this application in the name attribute.

Enable or disable the error collector.

Enable or disable the capturing of error events.

Reservoir limit for error events.

A list of fully qualified class names to be ignored. The maximum number of error class and message combinations that SHOULD be reported is 50. If more than 50 are listed, then only the first 50 SHOULD be used.

An optional map of fully qualified class names to list of strings matching a substring of the message of an error. The maximum number of error class and message combinations that SHOULD be reported is 50. If more than 50 are listed, then only the first 50 SHOULD be used.

Lists specific exceptions to not report to New Relic. The full name of the exception should be used, such as System.IO.FileNotFoundException.

Lists specific HTTP error codes to not report to New Relic. You can use standard integral HTTP error codes, such as just 401, or you may use Microsoft full status codes with decimal points, such as 401.4 or 403.18. The status codes should be equal to or greater than 400.

This can also be configured via environment variable, specifying multiple codes with a comma-separated list:

NEW_RELIC_ERROR_COLLECTOR_IGNORE_ERROR_CODES=401, 403.18

A list of fully qualified class names to be marked as expected. The maximum number of error class and message combinations that SHOULD be reported is 50. If more than 50 are listed, then only the first 50 SHOULD be used

An optional map of fully qualified class names to list of strings matching a substring of the message of an error. The maximum number of error class and message combinations that SHOULD be reported is 50. If more than 50 are listed, then only the first 50 SHOULD be used

A comma-separated list of status codes. The list may include integer ranges using a single dash (-), and will be inclusive of both the starting and ending integer in the range.

This can also be configured via environment variable:

NEW_RELIC_ERROR_COLLECTOR_EXPECTED_ERROR_CODES=401, 501-503

Use this sub-element to customize your agent attribute settings for error traces. This sub-element uses the same settings as the primary attributes element: enabled, include, and exclude.

Enable or disable high-security mode. Example:

<highSecurity enabled="true"/>

Alternatively, set the NEW_RELIC_HIGH_SECURITY environment variable in the application's environment:

NEW_RELIC_HIGH_SECURITY=true

Enable or disable strip exception messages. Example:

<stripExceptionMessages enabled="true"/>

Enable or disable the event recorder.

The maximum number of sampled transaction events the agent can store in memory at once. This will be the maximum number of transaction events the agent can send per minute.

Alternatively, set the MAX_TRANSACTION_SAMPLES_STORED environment variable in the application's environment:

MAX_TRANSACTION_SAMPLES_STORED=500

Use this sub-element to customize your agent attribute settings for transaction events. This sub-element uses the same settings as the primary attributes element: enabled, include, and exclude.

Enable or disable the event recorder.

The maximum number of sampled custom events the agent can store in memory at once. This will be the maximum number of custom events the agent can send per minute.

Alternatively, set the MAX_EVENT_SAMPLES_STORED environment variable in the application's environment:

MAX_EVENT_SAMPLES_STORED=500

• If you're configuring the agent for AI monitoring, we recommend setting the value to 100000.

Enable or disable the capture of custom parameters.

By default the agent automatically injects the browser agent JavaScript. To turn off automatic injection, set this attribute to false.

Use this sub-element to customize your agent attribute settings for browser monitoring. This sub-element uses the same settings as the primary attributes element: enabled, include, and exclude.

Use this sub-element to prevent the browser agent from being injected in specific pages. The element is used as follows:

<requestPathsExcluded>
  <path regex="url-regex-1"/>
  <path regex="url-regex-2"/>
  ...
  <path regex="url-regex-n"/>
</requestPathsExcluded>

The agent will not inject the browser agent into pages whose URL matches one of the specified regular expressions. The regular expression should follow Microsoft guidelines for the Regex class.

It is a reference to the virtual directory of the path in your application and not the full URL of the path you wish to exclude. For example, to exclude the pages in https://www.mywebsite.com/mywebpages/ you would simply insert /mywebpages/ as the path regex value.

The requestPathsExcluded element should be used in cases where it is impossible or undesirable to use the DisableBrowserMonitoring() call. To minimize a possible performance impact try to use as few regular expressions as possible and keep them as simple as possible.

Enable or disable slow query tracing.

Enable or disable transaction traces.

Defines the threshold for transaction traces. If a transaction takes longer than the threshold, it is eligible for being traced. See transaction trace basics for more about the rules governing traces.

The default value is apdex_f, which sets the threshold to four times the application's apdex_t value. For more information about apdex_t, see Apdex.

You can also set the threshold to be a specific time value in milliseconds.

Select a query tracing policy. Options are off, which records nothing; obfuscated, which records an obfuscated version of the query; or raw, which records the query exactly as it is issued to the database.

When true, the agent captures EXPLAIN statements for slow queries with durations exceeding explainThreshold. Note that enabling this feature can have performance implications because plans are captured for every transaction up to the maxExplainPlans value.

The agent collects slow query data for queries that exceed this threshold, along with any available explain plans, as part of transaction traces.

The maximum number of segments to collect in a transaction trace.

The maximum number of explain plans to collect per transaction.

By default maxStackTrace is set to 0, which disables stack traces as part of a transaction trace. If this value is set greater than 0, then stack traces will be captured for transaction traces.

Use this sub-element to customize your agent attribute settings for transaction traces. This sub-element uses the same settings as the primary attributes element: enabled, include, and exclude.

Use this sub-element to enable collection of datastore instance metrics (such as the host and port) for some database drivers. These are reported on slow query traces and transaction traces. The default value of attribute enabled is true.

Use this sub-element to enable collection of the database name on slow query traces and transaction traces for some database drivers. The default value of attribute enabled is true.

Use this sub-element to enable collection of the SQL query parameters on slow query traces. The default value of attribute enabled is false.

Alternatively, enable distributed tracing via the NEW_RELIC_DISTRIBUTED_TRACING_ENABLED environment variable in the application's environment:

NEW_RELIC_DISTRIBUTED_TRACING_ENABLED=true

By default, supported versions of the agent utilize both the newrelic header and W3C Trace Context headers for distributed tracing. The newrelic distributed tracing header allows interoperability with older agents that don't support W3C Trace Context headers. Agent versions that support W3C Trace Context headers will prioritize them over newrelic headers for distributed tracing.

If you do not want to utilize the newrelic header, setting this to true will result in the agent excluding the newrelic header and only using W3C Trace Context headers for distributed tracing.

Set the <spanEvents> element to false to disable via the newrelic.config file. This element is a child of the <configuration> element.

<configuration . . . >
  <spanEvents enabled="false" />
</configuration>

Set the NEW_RELIC_SPAN_EVENTS_ENABLED environment variable in the application's environment:

NEW_RELIC_SPAN_EVENTS_ENABLED=false

The trace_observer element identifies an observer host that is independent from the agent. For help getting a valid Infinite Tracing trace observer host entry, see Find or create a trace observer endpoint.

The trace observer may be configured using the NEW_RELIC_INFINITE_TRACING_TRACE_OBSERVER_HOST environment variable as well.

Enable or disable cross application tracing

Enable or disable the event recorder.

The maximum number of sampled span events the agent can store in memory at a time. This will be the maximum number of span events the agent can send per minute.

• This may be configured using the NEW_RELIC_SPAN_EVENTS_MAX_SAMPLES_STORED environment variable as well.

• We do not recommend configuring past 10k. The server will cap data at 10k per-minute.

• If you're configuring the agent for AI monitoring, we recommend setting the value to 10000.

  Importante

  This configuration option is only available in the .NET Agent v9.0 or higher.

Use this sub-element to customize your agent attribute settings for span events. This sub-element uses the same settings as the primary attributes element: enabled, include, and exclude.

Enable or disable HTTP request headers capture. Example:

Alternatively, set the NEW_RELIC_ALLOW_ALL_HEADERS environment variable in the application's environment:

<allowAllHeaders enabled="true" />
<attributes enabled="true">
   <include>request.headers.*</include>
</attributes>

Enable or disable all logging instrumentation features. If true, the individual sub-feature configurations take effect. If false, no logging instrumentation features are enabled.

Or use the NEW_RELIC_APPLICATION_LOGGING_ENABLED environment variable.

Use this sub-element to enable collection of logging metrics (such as Logging/lines) for common .NET logging frameworks. The default value of attribute enabled is true.

Or use the NEW_RELIC_APPLICATION_LOGGING_METRICS_ENABLED environment variable.

Use this sub-element to enable forwarding of your application's logs to New Relic. The default value of attribute enabled is true, you can also use the NEW_RELIC_APPLICATION_LOGGING_FORWARDING_ENABLED environment variable.

The default value of attribute maxSamplesStored is 10000, you can also use the NEW_RELIC_APPLICATION_LOGGING_FORWARDING_MAX_SAMPLES_STORED env variable for this setting. Set this to a lower value to reduce the amount of log lines sent (may cause log sampling). Set this to a higher value to send more log lines.

Each log receives the same priority as its associated transaction. Logs that occur outside of a transaction will receive a random priority. Some logs may not be included because they are limited by maxSamplesStored. For example, if logging maxSamplesStored is set to 10,000 and transaction 1 has 10,000 log entries, only log entries for transaction 1 will be recorded. If transaction 1 has less than 10,000 logs you receive all logs for transaction 1. If there is still space, you receive all the logs for transaction 2, and so on.

If after all the logs for sampled transactions are recorded, and they haven't reached the limit in maxSamplesStored, then log messages for transaction that were not in our sampling are sent. If there are any left, log messages outside of transactions are recorded.

Use the logLevelDenyList attribute (or the NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LOG_LEVEL_DENYLIST environment variable) to filter out log messages of the specified log levels. The value for this attribute is a comma-separated case-insensitive list of levels. Outside of the case, the log level string must exactly match the log level being filtered, wildcards and regex are not supported. For example, if the value was set to logLevelDenyList="debug,warn", any log messages with the log level of Debug or Warn will not be captured or forwarded, but a log with a level of Warning would still be sent to New Relic.

Use this sub-element, which is a child of the forwarding element, to configure the capture and fowarding of logging context data (custom attributes), in agent versions 10.4.0 and higher.

Set the enabled attribute to true to enable capture and forwarding of logging context data to New Relic, you can also use the environment variable NEW_RELIC_APPLICATION_LOGGING_FORWARDING_CONTEXT_DATA_ENABLED. The default value is false.

The include attribute is a comma-separated list of names of attributes to include when context data capture is enabled, you can also use the environment variable NEW_RELIC_APPLICATION_LOGGING_FORWARDING_CONTEXT_DATA_INCLUDE. The default value is an empty string, which means "include everything."

The exclude attribute is a comma-separated list of names of attributes to exclude when context data capture is enabled, you can also use the environment variable NEW_RELIC_APPLICATION_LOGGING_FORWARDING_CONTEXT_DATA_EXCLUDE. The default value is an empty string, which means "exclude nothing."

The include and exclude lists follow the same precedence rules as other agent attributes configuration.

Use this sub-element, which is a child of the forwarding element, to configure adding your labels (tags) to agent-forwarded logs, in agent versions 10.34.0 and higher.

Set the enabled attribute to true to enable adding your labels to agent-forwarded logs. You can also use the environment variable NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LABELS_ENABLED. The default value is false.

The exclude attribute is a case-insensitive, comma-separated list of label names to exclude when you enable labels. You can also use the environment variable NEW_RELIC_APPLICATION_LOGGING_FORWARDING_LABELS_EXCLUDE. The default value is an empty string, which means "exclude nothing". This attribute does not support wildcards or regex.

Use this sub-element to enable decoration of your application's logs with New Relic linking metadata. The default value of attribute enabled is false. Some additional configuration changes are required for local log decoration, please see .NET: Configure logs in context for more information.

Use this sub-element to enable all input and output for LLM events to be sent to New Relic. The default value of attribute enabled is true. Content recording is disabled in High Security Mode.

Note that if content recording is disabled, LLM token counting must be provided by the the customer, by calling the SetLlmTokenCountingCallback API. If this callback is not provided, the agent will not be able to provide LLM token counting.

<aiMonitoring enabled="true">
  <recordContent enabled="false" />
</aiMonitoring>

This can also be configured via environment variable:

NEW_RELIC_AI_MONITORING_RECORD_CONTENT_ENABLED=false

For more information, see Name your .NET application.

<appSettings>
  <add key="NewRelic.AppName" value="Descriptive Name" />
</appSettings>

Designates an alternative location for the config file outside of the local root of the app or global config location. The location entered must be an absolute path.

<appSettings>
  <add key="NewRelic.ConfigFile" value="C:\Path-to-alternate-config-dir\newrelic.config" />
</appSettings>

For more information, see Name your .NET application.

{
  "NewRelic.AppName": "Descriptive Name"
}

Designates an alternative location for the config file outside of the local root of the app or global config location. The location entered must be an absolute path.

{
  "NewRelic.ConfigFile": "C:Path-to-alternate-config-dir\newrelic.config"
}