On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
1 rates

New in 4.5.9 You can now configure simple POCO or ASP.NET business transactions for the .NET Agent for Linux through the Controller UI.

The .NET Agent for Linux version 4.5.9 works with Controller version 4.4.1 and higher, but the customizable transaction detection and configuration capabilities require 4.5.2 and later versions of the Controller.  For Controller versions 4.4.2 to 4.5.1 and the .NET Agent for Linux, AppDynamics defaults to using the first two segments of the URI for ASP.NET business transaction naming. 
Configuring ASP.NET business transactions is a feature preview in this agent version, recommended for pre-production systems. To enable this feature, see Enable Feature Previews.

ASP.NET Business Transaction Configuration

Define Custom ASP.NET Business Transactions Using the Controller UI

You can create ASP.NET business transactions detection include and exclude rules with criteria that match HTTP Requests against:
  • Method 
  • URI
  • HTTP parameter
  • Header 
  • Cookie

Transaction splitting is supported for the above HTTP request criteria.

Although the following HTTP request options appear in the dropdown list, they are not supported at this time by the .NET Agent for Linux. There is no effect if you configure them in the UI. 

  • Hostname 
  • Port
  • Class name

You customize business transactions for the .NET Agent for Linux in a manner similar to other agents. Click Configure > Instrumentation > Add Rule and then choose to create either an include or exclude rule.  

Example ASP.NET Business Transaction Detection Rule

The following screeenshots show how to create a .NET Agent custom match rule that uses an ASP.NET entry point to exclude all requests whose URI equals /healthcheck. 

In this screenshot of the Rule Summary, we specify that this is an exclude match rule. You must create an include rule before you can create an exclude rule to omit some of the transactions monitored by the include rule. 

Here we specify the HTTP request criteria by choosing to use the URI attribute of the HTTP request to compare against. Valid criteria are Method, URI, HTTP parameter, Header, and Cookie. You can split the transactions based on these request match criteria.

The following screenshot specifies the HTTP request match criteria where the URI equals /healthcheck

POCO Business Transaction Configuration

Define Custom POCO Business Transactions Using the Controller UI

Using the .NET Agent for Linux, you can create POCO business transaction rules that match synchronous or asynchronous transactions by:
  • Method name
  • Class name
Although the following Match Classes options appear in the dropdown list, they are not supported at this time. There is no effect if you configure them in the UI: 
  • that implements an interface which
  • that extends a super class that
  • that has an Annotation which
Also, the following are not yet supported:
  • Transaction splitting using method/class data
  • Background jobs
  • Interface, base class or annotation POCO conditions

Example POCO Business Transaction Detection Rule

The following screeenshots show how to create a .NET Agent custom match rule that uses a POCO entry point to include all requests whose class equals MyCompanyJobs.JobProcessor and the method name equals OnEvent

In this screenshot of the Rule Summary, we specify that this is an include match rule. You must create an include rule before you can create an exclude rule to omit some of the transactions monitored by the include rule. 

Here we configure the rule to match classes using the with a Class Name that Match Classes option, which is the only Match Classes option currently supported by the .NET Agent for Linux. 

The following screenshot specifies the Match Class & Method match criteria to match classes with a class name that equals MyCompanyJobs.JobProcessor and the method name equals OnEvent

Transaction splitting is not currently supported for the .NET Agent for Linux.
  • No labels