Business Transaction Discovery Sessions are supported for Java and .NET applications. These sessions help a Performance Analyst identify candidate transaction entry points when automatic discovery does not detect a proprietary framework, background process, scheduled task, or other nonstandard execution path.
During a discovery session, the Application Agent observes executed application code and allows the analyst to browse relevant classes and methods. The selected method can then be used to create or refine a Custom Match Rule, establishing a new Business Transaction entry point with appropriate naming and scope.
Java and .NET agents provide the runtime instrumentation and class-method visibility required for this workflow. C++, PHP, and Node.js applications have their own supported monitoring and transaction-detection capabilities, but they do not use the Business Transaction Discovery Session feature referenced in this question.
Discovery sessions should be run for a controlled period while representative application traffic exercises the target code path. The resulting class and method information can then be reviewed before creating a permanent transaction detection rule.
Relevant CAAPA Study Guide topics include Business Transaction Discovery Sessions, Java Agent, .NET Agent, Class and Method Browsing, Custom Match Rules, Entry-Point Detection, and Transaction Naming.
