Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Vasu B (SriniA28)
Nationale-Nederlanden Services NV

Nationale-Nederlanden Services NV
NL
SriniA28 Member since 2019 1 post
Nationale-Nederlanden Services NV
Posted: Mar 15, 2019
Last activity: Mar 15, 2019
Posted: 15 Mar 2019 9:36 EDT
Last activity: 15 Mar 2019 10:28 EDT
Closed

PEGA0069: Production system is slow and more PEGA0069 alerts in logs

Hi,

Production application is slow (sometimes it is good and sometimes is slow for same operations). Most of the alerts coming in production are PEGA0069 and PEGA0037.

Can someone suggest please whether it's issue with Network/Database or Application?

Thanks,

Vasu

To see attachments, please log in.
System Administration

Posted: 5 years ago
Posted: 15 Mar 2019 10:03 EDT
Arvind Malav (malaa) Technical Manager
Pegasystems Inc.
IN

Apart from above comment, you should review PDC if configured to see which are alarming events/alerts or AES if you have .

To see attachments, please log in.
Posted: 5 years ago
Posted: 15 Mar 2019 10:28 EDT
Abhinav Gupta (Abhinav7)
PEGA
Manager, Technical Support - Platform Service Engineering
Pegasystems Inc.
IN

Hi,

Analysing pega alert log will give better insight about that.Since It is not good approach to share alert logs here so please raise an SR with GCS and attach pega rules and alert logs.

If your alert log contains a large number of PEGA0069 messages, a problem on the server, network, or client might be causing screens to take a long time to load. Using the message text, compare the load duration to the server duration to narrow down the issue to the server, client, or network. The action specified in the alert message can also help you determine which screen or action caused the alert.
Other alerts that are triggered by this screen load have the same requestor ID and page load counter as the PEGA0069 alert. You can use this information to correlate those alerts to the PEGA0069 alert.It will be dependednt on some other alert.

Pega0037 shows issue with cache.

You can try to tune cache settings.

Show More

Hi,

Analysing pega alert log will give better insight about that.Since It is not good approach to share alert logs here so please raise an SR with GCS and attach pega rules and alert logs.

If your alert log contains a large number of PEGA0069 messages, a problem on the server, network, or client might be causing screens to take a long time to load. Using the message text, compare the load duration to the server duration to narrow down the issue to the server, client, or network. The action specified in the alert message can also help you determine which screen or action caused the alert.
Other alerts that are triggered by this screen load have the same requestor ID and page load counter as the PEGA0069 alert. You can use this information to correlate those alerts to the PEGA0069 alert.It will be dependednt on some other alert.

Pega0037 shows issue with cache.

You can try to tune cache settings.

Thanks,
Abhinav


Show Less
To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice