Custom Match Rules for ASP.NET Transactions
Custom match rules provide greater flexibility for transaction naming. When you define a match rule, Splunk AppDynamics uses the rule name for the business transaction name.
See Custom Match Rules for general information on how to create custom match rule.
When Splunk AppDynamics detects a request matching your specified criteria, it identifies the request using your custom name. You can use the following criteria to match transactions:
Method: Match on the HTTP request method, GET, POST, PUT or DELETE.
-
Disable automatic discovery for ASP.NET transactions.
-
Create an exclude rule for the method you don't want: GET or POST.
URI: Set the conditions to match for the URI.
-
- For rules on regular expressions for .NET, see .NET Framework Regular Expressions.
- Optionally click the gear icon to set a NOT condition.
- You must set a URI match condition in order to use transaction splitting.
HTTP Parameter: Match on HTTP parameter existence or a specific HTTP parameter value.
Header: Match on a specific HTTP header's (parameter's) existence or a specific HTTP header value.
- Hostname: Match on the server hostname. Optionally click the gear icon to set a NOT condition.
- Port: Match on the server port number.Optionally click the gear icon to set a NOT condition.
- Class Name: Match on the ASP.NET class name. Optionally click the gear icon to set a NOT condition.
- Cookie:Match on cookie existence or specific cookie value.
- Hostname, Port, and Class Name options are non-functional in the .NET Agent 4.5.9 for Linux.