Poor performance with connector
Users experience extremely slow performance.
PegaRULES-ALERT log shows Pega0001 (slow user interaction) with KPI of 10,000 or higher (milliseconds) for affected users.
Steps to Reproduce
A third-party issue is the cause of this problem. Further analysis of the ALERT log shows Pega0020 with similar KPI on the same requestor ID, indicating a slow external service connection.
Looking at the PAL stats provided in the alert (example)
This is the number of milliseconds for the external service connection - 1 millisecond to map the outgoing response, over 30 seconds to receive a response from the external client, and 2 milliseconds to map the incoming response to corresponding pega properties.
The external service is the cause of the slow performance. This issue must be addressed by the provider of the external service.
0% found this useful