Hi All,

I find myself again searching for information on preventing unnecessary logs from being written with the upgrade to 23.1.2.  This time its

System Pulse Acknowledgement - Message Received

So I found the following information in 23.1.2 Resolved Issues for System Administration

After deploying a ruleset versioning update, the new rules were not being picked up by the queue processor and the system runtime context continued to be the previous ruleset version. This type of issue occurs when the SystemPulse fails to propagate the latest version of the rule to all nodes in the cluster, leading the system to utilize the existing version of the rule. In order to capture whether the deployed rules are propagated to all the nodes in the cluster, additional diagnostic log messages have been added. These loggers handle defined rule update pulse types for diagnostic information, CACHE, RFDEL, IMPRT, CLDEC, PURGE, DSMST, and are based on the environment's production level and DASS: systempulse/rulesUpdate/logAcknowledgement/enabled.  Logging has been enabled by default for production level >= 4 (i.e. PRE-PROD or PROD) and disabled by default for lower environments.

But yet again, no information on which owning ruleset this DSS should be created under and whether this can be applied without a restart and whether the value to disable should be set as false or something else.

We have seen since the upgrade 05/06 (8.6 > 23.1.2) upto 600k log entries per day for this logging, which quite frankly is ridiculous.

The other concern we've seen is that the number of minor garbage collections has also increased from around 30k per day to 200k per day.  And we can see the following log entries that seem to contribute to this GC run.

14/06/2024 15:42:57.566

2024-06-14 15:42:57,566 [oyant_bouman.event-3] [ ] [ ] [ ] ( SystemPulse) INFO - System Pulse Acknowledgement - Message Received: [createDate:Fri Jun 14 15:42:56 BST 2024, pulseType:RFDEL, pzInsKey:, sourceNode:pega-kn-p2, systemName:, className:Data-Content-Image, parameters:FileToDelete=/datacontent/image/gen_1f6b4d9f89848ef527158b341b88df93_applicationdata_0.js, tenantID:null]

This log entry seems to appear upon a user simply logging in to the system and we've no idea what its doing.  The FileToDelete param is obviously different for each user logging in.

So if someone can answer the question of what we need to do to turn this logging off that would be great.  Also if anyone knows if these are related that would be fantastic to know also.

Thanks
Craig