Using AppDynamics to monitor business transactions in a Pega Application
Hi
Does anyone have any experience of using AppDynamics to monitor business transactions in a Pega Application?
We have successfully configured AppDynamics to trace a http request, but at its simpliest level it appears to need a unique string to identify the http request as the start of a specific business transaction.
For example we are using CPM-C 7.13 on a Pega Platform 7.1.8 installation and our Phone number search http request string generates a specific string 'ValidateSearchInput' that we can use, but it is not as easy for wrap up for example.
Does anybody have experience of this combination of technologies that can help?
Other approaches we are considering include:
Hi
Does anyone have any experience of using AppDynamics to monitor business transactions in a Pega Application?
We have successfully configured AppDynamics to trace a http request, but at its simpliest level it appears to need a unique string to identify the http request as the start of a specific business transaction.
For example we are using CPM-C 7.13 on a Pega Platform 7.1.8 installation and our Phone number search http request string generates a specific string 'ValidateSearchInput' that we can use, but it is not as easy for wrap up for example.
Does anybody have experience of this combination of technologies that can help?
Other approaches we are considering include:
- Class based monitoring (though we are not sure how this will work to monitor a business transaction in AppDynamics)
- Wrapping the html request with another Class (upgrade etc might be an issue)
- Logging directly to a database using asynchronous requestors (but then we have to build the reports, dashboard, alerts etc)
Ideally we would be able to:
- Add a unique string to identify the start and end of a transaction
- Add the unique string to a business flow or an activity
Regards Alan
Pegasystems Inc.
US
I do not have personal experience with this but from what I see on discussions amongst Pega development is that they only employ this tool at the "application class level" due to the fact that CPU usage is significantly low. You can then deploy "custom timers" that span a series of activities. Very powerful at this level.
I suggest you explore "Class based monitoring" as opposed to trying to change your URL parameters to support the tool. Also, with "custom metrics", you can send any integer-based value to the agent to use for tracking transactions.