Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

How do I detect and correlate Business Transactions for PingAccess (Ping Identity)?

How do I detect and correlate Business Transactions for PingAccess (Ping Identity) instrumentations?

 

Table of Contents

Problem

Requirement

Configuration

 

Problem

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.

 

Requirement

This configuration should work with PingAccess 4.x and 5.x version.

 

Configuration

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]

Instrumentation_-_AppDynamics-2.jpg

Instrumentation_-_AppDynamics-1.jpg

 

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. 

ignore-exitcall-on-reentry=false

 

Version history
Revision #:
3 of 3
Last update:
‎03-13-2019 10:04 PM
Updated by:
 
Labels (1)
Comments

Worked perfectly fine thanks.