AppDynamics Inc.

Skip to end of metadata
Go to start of metadata

This topic introduces .NET entry points and the way that they are used in business transaction detection. If the auto-discovered entry points don't include all your critical business transactions, use custom match rules to customize entry point discovery.

.NET Entry Points

AppDynamics detects entry points in the following places:

  • On originating tiers, the method or operation that marks the beginning of a business transaction is an entry point. In most cases, this type of entry point maps to a user request or action such as "View/Cart". Entry points on originating tiers define the business transaction name.
  • On downstream tiers, entry points correlate to incoming http calls, web service requests, and other communications from instrumented tiers.

The App Agent for .NET (agent) automatically detects entry points for the frameworks listed as automatically discovered business transactions. See Supported Environments and Versions (.NET).

If the agent detects an entry point on the originating tier, it registers a business transaction with the Controller. The Controller displays the business transaction in the Business Transactions List. If an entry point correlates to an upstream exit point, such as an exiting service call, the agent includes it as part of the existing business transaction.

If you need to monitor transactions not automatically discovered by the App Agent for .NET, you can customize entry point detection. See Organizing Traffic as Business Transactions to learn how to plan your business transactions. After you have identified the critical business transactions for your application, create custom match rules for them to enable transaction detection.

To create custom match rules for .NET entry points

1. Click Configure > Instrumentation > Transaction Detection.

2. Click the .NET - Transaction Detection tab.

3. From the Select Application or Tier list at the left, click either:

  • an application, to configure transaction detection for all tiers in a business application.
  • a tier, to configure transaction detection at the tier level. At the tier level click Use Custom Configuration for this Tier. AppDynamics copies the application configuration to the tier level so that you can modify it for the tier.

4. Use the Custom Match Rules pane to add and remove business transaction match rules.

For details on types of .NET entry points and how to setup custom match rules, see:


Learn More