As of 4.5.9, you can 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 later, 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.

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:

Transaction splitting is supported for the HTTP request criteria. 

  • Method 
  • URI
  • HTTP parameter
  • Header 
  • Cookie

Although these HTTP request options display in the dropdown list, they are not supported 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 similarly as other agents. Click Configure > Instrumentation > Add Rule and then select to create either an include or exclude rule.  

ASP.NET Business Transaction Detection Rule Example

This example shows how to create a .NET Agent custom match rule that uses an ASP.NET entry point to exclude all requests whose URI equals /healthcheck. 

This Rule Summary specifies 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. 

You specify the HTTP request criteria by using 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.

This HTTP request match criteria specifies where the URI equals /healthcheck

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 these Match Classes options display in the dropdown list, they are not supported. However, 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
Additionally, these criteria are not supported:
  • Transaction splitting using method/class data
  • Background jobs
  • Interface, base class or annotation POCO conditions

Example POCO Business Transaction Detection Rule Example

This example shows 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

This Rule Summary specifies 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. 

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

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

Transaction splitting is not supported for the .NET Agent for Linux.