App Agent Node Properties (A)

Enable database detection and naming for ODP.NET backends labeled Unknown0.

Disable agentless Transaction Analytics on a particular node or tier.

By default, the Java Agent, .NET Agent, and Node.js Agent set business transaction correlation data in a cookie for HTTP responses, except when the JavaScript Agent has already set an isAjax:true header in the request. When it finds the isAjax:true header, the agent sets the correlation metadata in the XHR header.

For cross-origin AJAX requests, the JavaScript Agent does not set isAjax:true so that the app agent doesn't write correlation data to the header of those responses.

Set always-add-eum-metadata-in-http-headers to true to configure the app agent to write business transaction metadata to the XHR header and in a cookie even if the request is considered cross-origin.

This property specifies the per minute upper limit on the number of SQL queries that collect parameter data for analytics. The number is a cumulative total. It is not the number of distinct SQL queries, but the overall number of invocations of the SQL queries that have been configured to collect analytics data.

This property provides a time-out value that comes into play when you have added global transactions to your application using APIs from the AppDynamics SDK. In the event that the added transaction spawns additional threads that do not return or complete, this property provides a safety valve time-out value. The value is in seconds. The removeCurrentThread method is invoked after the specified timeout period.

This property provides a time-out value that comes into play when you have added global transactions to your application using APIs from the AppDynamics SDK. In the event that the added transaction does not return or complete, this property provides a safety valve time-out value. The time-out value is in seconds. The endTransaction method is invoked after the specified time-out period.

This property increases the metric limit for the .NET Agent for Linux.

This property provides a switch to flip the entire reactor instrumentation. If you set it to false, all rules pertaining to reactor thread correlation are unapplied.

This property provides a switch to apply in process correlation rules for prospective thread hand-offs. By default these rules are disabled. These rules can only be applied if 'apply-reactive-rules' node property is set to true. If 'apply-reactive-rules' property is set to false, setting this property to 'true' will not apply any rules.

When you set this property, ASP.NET Core entry instrumentation is restored to RequestServicesContainerMiddleware.Invoke for .NET Core 2.1 and 2.2 apps. You can use this when Business Transactions are missing from .NET Core apps after you upgrade an agent.

If true, causes the agent to identify ASP.NET Core on the full framework business transactions as Controller/Action.

If true, causes the agent to identify ASP.NET Core on the full framework business transactions as Area/Controller/Action.

If true, causes the agent to identify ASP.NET MVC business transactions as Controller/Action. See Name MVC Transactions by Area, Controller, and Action.

If true, causes the agent to identify ASP.NET MVC business transactions as Area/Controller. See Name MVC Transactions by Area, Controller, and Action.

Enable or disable detection of asynchronous exit points. See Asynchronous Exit Points for .NET.

This class name and method name combination marks the end of an asynchronous distributed transaction. Use the format ClassName/MethodName. For example, foo/bar where foo is the class name and bar is the method name.