Support Article
DSS is generated for AES push usage
SA-68626
Summary
Multiple new Dynamic System Setting (DSS) entries are generated for Autonomic Event Services (AES) push usage.
According to the PushLogUsageData activity, node ID changes constantly and hence, new DSS entries are generated.
Error Messages
Not Applicable
Steps to Reproduce
- Open the DSS landing page.
- Filter for AES entries.
Root Cause
This behavior is as per Pega product design.
Resolution
Here's the explanation for the reported behavior:
AESRemote rules, that ship with Pega 7.4, push summarized log-usage data from all the nodes and require a unique DSS for each node to track when data was last pushed. Thus, new DSS is created as new cloud nodes are created.
Any DSS for a node which no longer exists can be deleted.
Published November 30, 2018 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.