How Declarative Cache count is calculated in Memory Management
We got Pega 17 alert and through DSS setting we updated it to 5000. For couple of months, it was fine, but later we started again getting Pega 17 alerts.
when we checked across all the production nodes, we see that the Declarative Cache count under memory Management is 6800+ approximately.
Now we can set the DSS setting to 10000, But this is kinda of like suppressing the alert each time, it reaches the threshold.
We wanted documentation\reference materials on how the Declarative Cache count and other cache count is calculated and displayed under Memory Management. Also Pega must be using some logic to identify and throw each and every alert.
We raised an SR with GCS, asking for any documentation\reference material available for all the Pega alerts. This will help us understand the root cause of each alert better and take preventative steps during development phase itself.
However, GCS closed the SR and advised to post a query in Community.
If any one has the logic details on one or more of the Pega alerts, please kindly share.
***Edited by Moderator: Pallavi to update SR Details***
This pega0017 alert occurs when certain cache sizes configured are insufficient for the environment. As a result of undersized caches, the system is forced to purge items from the cache regardless of usage. This can also cause an unusually high number of cache misses and negatively impact system performance.
Can you please create the below DSSs with the following Setting Purposes and Values (modify the value if the DSSs are already exist).