1. Define the custom match rule on the .NET class/method that is the most appropriate entry point for the business transaction
2. On an originating tier, a POCO entry point is the method that starts the business transaction. If the POCO entry point is on a downstream tier, it may correlate to an upstream exit point.
3. It is important to choose a method that begins and ends every time the business transaction executes.
4. Good candidates for POCO entry points include the following:
a. A timer in a Windows service that executes a database call to check for new records to process. For example, an order processing system that periodically checks for new orders in the system.
b. A loop in a standalone application that batch processes records via a web service call. For example, an expense reporting system that loops through approved expenses to submit them for reimbursement.
c. A method in a web application that executes every time a client connects.
5. Navigate to Configuration > Discovery Tools and click Start Discovery Session.
6. Select the nodes where you want the agent to discover business transactions.
7. After creating the POCO custom match rule, use Copy or Configure all Tiers to use this Configuration on the Transaction Detection tab to copy the POCO rule to one or more tiers.
a. The Transaction Discovery window doesn't automatically display .NET transactions before you open the Class/Method Browser.
8. Click Class/Method Browser.
9. Select your match criteria: interface name, superclass, annotation, or class name.
10. Specify a string to match and press Enter.
a. The .NET Agent searches using a case-sensitive substring match. Wildcards are not allowed.
b. You can leave the Transaction Discovery window while the agent searches for methods and return to it later.
c. The Controller displays matching classes from the assemblies that have been JIT-compiled.
11. Expand a class to display methods to instrument.
12. Right-click a method name and click Create Poco Rule.
13. The New Business Transaction Match Rule window opens. The Transaction Discover Tool automatically populates the Match Classes and Method Name fields.
14. If the auto-discovered entry points don't include all your critical business transactions, use custom match rules to customize entry point discovery.