Hello,
I have a flow which is recognized as business transaction, and i want to define a new BT for a private method in this flow.
I did it via configuration-->instrumentation-->Custom Match Rules-->POJO type for the relevant class and method in equals.
However this transaction is not recognized.
Whats wrong with my definition.
Thanks
Hi Boris
I'm not sure exactly why you want to do this and I assume you have read our documentation on business transactions and understand their utility in helping to monitor your application functionality. The docs:
https://docs.appdynamics.com/display/PRO40/Organize+Traffic+as+Business+Transactions and
https://docs.appdynamics.com/display/PRO40/Configure+Business+Transaction+Detection
However, it kind of sounds like you might be interested in using one of our data collectors: Method Invocation Data Collector or an Information Point depending on exactly what you are trying to measure.
Docs describe the differences and how to configure each one:
https://docs.appdynamics.com/display/PRO40/Data+Collectors+Versus+Information+Points
https://docs.appdynamics.com/display/PRO40/Configure+Data+Collectors
Hello,
By default, the transaction discovery for Spring Bean-based requests is turned off.
Try this to enable: https://docs.appdynamics.com/display/PRO40/Spring+Bean+Entry+Points
Hi Boris,
- If i understood the requirement, the scenario is Class1.Method1 (Servlet) is discovered already as business transaction in controller UI and you want to monitor the spring bean Class2.Meethod2 which is invoked by discovered BT and shown part of snapshot call graph stack trace.
- If above said is the case, we confirm we do not support nested API call as separate BT when the parent class/method is already a discovered BT with default config settings.
- However you can try the following and see if that helps: - Under Configure -> Instrumentation -> Transaction detection -> Entry points , select the checkbox "Enable servlet filter detection" and see how it goes, Please be sure that above setting could result in all nested calls as separated BTs if the corresponding nested entry point auto discovery Or custom rule is defined, request you to check the behavior for new load on custom rule and see how it goes and customize other entry points (struts, ejb etc) as required in controller UI.
- Other option is define Service end points as suggested in doc link https://docs.appdynamics.com/display/PRO40/Monitor+Service+Endpoints and see if that helps which helps to monitor execution of nested API custom SEP rule separately
Let us know if that information helps.
Regards, Arun