Updated on 6/13/2018
find-entry-points node property to configure missing entry points for any business transactions (BTs) that are not detected out of the box. This node property enables additional logging about the call stack of the application’s executing code. Use this information to identify potential entry points when the default automatic detection is insufficient, such as when the application to be monitored consists of older Java programs, unsupported frameworks or backends, or other non-J2EE compliant environments.
Three rules to keep in mind:
NOTE: Do not pick a method that never ends, such as a run () method that waits on a user request! See: POJO Entry Points.
find-entry-pointsproperty to true.
com.xyz.abc.domain.pqr.Healthand method run.
Note: Setting the property value to true causes verbose logging to be output until the value is switched to false, so it is unwise to leave this property value set to true.
If the application has no known exit calls, such as no HTTP, web services, JDBC, etc, then no call stacks are logged when you run find entry points.
To work around this limitation, set a custom exit point to force the logging of the associated call stack, then run find entry points again. The log entry at the top of the call stack should be your custom exit point. This works best when you know a method in the business functionality or user request that you are trying to measure. See Configure Custom Exit Points.
Published on 2/13/2015
Updated for 4.4 on 6/13/2018