Manage Transaction Call Graphs
- The call graph capture utilizes CPU and memory. It might affect the agent performance.
- This is applicable for Java rule with Entry Point as POJO.
- This option is available for the Java tiers only.
Call graphs allow you to automatically find all potential entry points that are hitting instrumented exit points or loggers. Use this option when you suspect that some traffic is not being detected as business transactions. To view call graphs in the Controller UI:
- Navigate to .
- Select a tier from the Tier tab.
- From the call graphs list, open a call graph to open the associated stack trace.
- Select a method from the stack trace and this will automatically populate the class and method field of the current detection rule.
- Configure the rule priority, scope, and save the rule. For information on rule priorities, see Transaction Detection Rule Priorities and Scope Configuration Model. You can start seeing the missing business transaction as soon as you save the rule.
- To change the call graph capture duration, configure the find.entry.point.session.window.size Controller property. In this property, specify the number of minutes for the call graph capture duration.Once the call graph session begins, you can see call graphs within a few minutes.
- To change the maximum number of call graphs that can be stored per tier, configure the find.entry.point.max.callgraph.tier Controller property. In this property, specify the number call graph that you want to capture and store for a tier. Make a note that the agent captures only 100 call graphs per session.