Ping Access is a Federated Access Management product from Ping Identity. Due to the low latency nature of the product, the underlying implementation of this does not use standard J2EE frameworks (e.g., Servlets or Apache/JDK HTTP Client etc.). Out of the box, the AppDynamics Agent will not detect or correlate any Business Transactions or exit calls when you instrument PingAccess. Custom configuration is required to get visibility into PingAccess until AppDynamics supports this.
This configuration should work with PingAccess 4.x and 5.x version.
1. Create a custom POJO entry rule. Refer to our documentation for instructions.
Name: PingAccessHTTPEntry Class : com.pingidentity.pa.core.interceptor.HTTPClientInterceptor Method : handleRequest Split on Getter Chain : Param index : 0 Getter chain: getRequest().getUri().split(\/).[0,1]
2. Replace attached custom-activity-correlation.xml at <agent-install-dir>/ver.../conf
3. Add an App Server Agent Node property. Refer to our documentation for instructions.