cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

Knowledge Base

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
Last update:
‎03-13-2019 10:04 PM
Updated by:
Labels (1)
By replying you agree to the Terms and Conditions of the AppDynamics Community.
Comments

Worked perfectly fine thanks.

Hey There, 

I recently integrated my Ping Access server with Appdynamics. I am able to the business transaction thanks to the steps listed above. But after i intregated my Ping Access server with Appdynamics,  the Ping Access is taking more than 100s to restart. Has this happened to anyone? Can you give me suggestion on how to resolve this issue?

I have followed the steps to configure this but I'm not sure what I should expect to see in the Business Transactions. How can I tell that it's set up properly?

I am seeing a new type of Business Transaction labeled "All Other Traffic - PingAccess" but when I go to expand it, the URL field is blank and only one node is listed (we have multiple PingAccess nodes).

Hi @Araceli.Garcia ,

 

You are seeing Business Transaction labeled "All Other Traffic - PingAccess" because of the business transaction limit being hit. You can refer this documentation link https://docs.appdynamics.com/display/PRO45/Business+Transactions#BusinessTransactions-btlimits to clean up and manage transactions.

For now, the "All Other Traffic - PingAccess" business transaction dashboard should show calls per minute, error per minute, etc. metrics. 

 

Thanks