ASP.NET Web Service Entry Points

AppDynamics automatically detects entry points for client requests to ASP.NET web services. If the request occurs on an originating tier, the method or operation marks the beginning of a business transaction and defines the transaction name. For more information on originating tiers, see Configure Business Transaction Detection for .NET.

When web service calls execute on a downstream tier, AppDynamics includes them as part of the business transaction from the originating tier.

Automatic Naming for Web Service Transactions

By default, the AppDynamics auto-detection naming scheme identifies all web service transactions using the service name and operation name:

ServiceName.OperationName

For example, a web service for a travel website books reservations from client front ends.

You can rename or exclude automatically discovered transactions from the business transaction list.

Custom Match Rules for ASP.NET Web Service Transactions

Custom match rules provide flexibility for ASP.NET web service transaction naming. When you define a match rule, AppDynamics uses the rule name for the business transaction name.

To access the Custom Match Rules pane, see 'To create custom match rules for. NET entry points' on .NET Business Transaction Detection.

To create an ASP.NET web service custom match rule

1. In the Custom Match Rules pane, click the plus symbol (+) to add an entry point.
2. Click Web Service in the dropdown. Click Next.
3. Name the New Business Transaction Match Rule.
   
   • AppDynamics uses the rule Name to name the BT.
   • The Controller enables the rule by default. Disable it later if needed.
   • Set the Priority for the match rule. AppDynamics applies higher priority rules first.
4. Set one or more of the following match criteria. When AppDynamics detects a request matching your specified criteria, it identifies the request using your custom name.
   
   Web Service Name
   
   • For rules on regular expressions for .NET, see .NET Framework Regular Expressions.
   • Optionally use the gear dropdown to set a NOT condition.
   Operation Name
   • For rules on regular expressions for .NET, see .NET Framework Regular Expressions.
   • Optionally use the gear dropdown to set a NOT condition.
   
   For example, to report all operations for a TravelService, such as SearchTravel and BookTravel, as one business transaction:
   
5. Click Create Custom Match Rule.
   The rule appears in the Custom Match Rule list. The business application or tier you customized displays a green check in the Select Application or Tier pane.
   

After the agent receives the updated configuration, it discovers the new business transaction and displays it in the Business Transactions list.