Question
amazon.com
US
Last activity: 27 Jun 2016 14:32 EDT
TP90 Graphs in AES?
We are looking at trying to graph browser response time by operator and requested resource. Does anybody know if AES collects this data or if we need to come up with some log-analysis from our webserver logs?
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems
IN
Currently AES only captures the time taken on server for every interaction and plots the graph for the same. It also uses this to co-relate with the alerts generated by the system.
If by browser response time you are indicating the taken on the browser as well, then that is currently not available in AES though there are plans to add that in a future release.
amazon.com
US
Thanks Rajiv,
What kind of timeline are we looking at re: AES backlog item?
amazon.com
US
Do you think it would be possible to create a custom logger in the prlogging.xml configuration in order to log request metrics?
Pegasystems
IN
Not sure. Copying Karen Davie
What is a 'requested resource'?
Pega does not presently capture 'per click' or 'per resource' data. If you want aggressive collection of JVM resources you'd best look at third part tools such as Dynatrace Pure Path.
Pega aggregates data per requestor (session) in PAL stats and asynchronously persists PAL stats once per hour and on session end to class log-usage / table pr_perf_stats. Log usage data includes requestor ID, snapshot date/time and operator ID. If you report on log-usage data you can get 'per operator' aggregate performance, but not per-click/per-resource.
PRPC sends AES a daily summary of log-usage data as well as every alert and exception. Core PRPC has code in the HTTP API to track average server response to browser requests. Every two minutes PRPC sends AES a health status message every two minutes with CPU, memory usage and recent average HTTP response.
I don't see "AES enhancement" here as there's no suitable data source in PRPC. Suggest you elaborate use case and business need.
amazon.com
US
We want to know which features are being used more heavily. So by "resource" we mean the Section/Harness/Action such as it can be captured in the URL minus the session ID.
We don't capture section / harness in the URL.
If you want to know which flow-actions are completed most frequently look at work history.
There may be some internal data on rule usage that will be of value but it is not documented.