Persistance of Audit Log - Impact on performance

[robert_warde4]

We are missing valuable  data in the audit log. Apparently the audit log data is only held in cache and as the volumes of data increase less and less information is available. However, this is very useful as it is the only record of any adapter processing and associated errors. Without this the rest of the data is meaningless.

This can be persisted

1314974 - Successful asynchronous messages - audit log persistence

1982452 - Audit Logs for successful synchronous messages with log versions to be persisted/archived if audit log memory cache is disabled

My question....Does anyone anyone have any experience with persisting audit log data AND has there been any impact on performance. SAP say this will impact performance but I would like to know by how much.

Many thanks

[Former Member · Accepted solution]

Hi,

I see that this message was sent on the 22 of June? So my guess is that your archiving has been setup and is running? Because this will archive it.

Please have a look at how aggressive your archiving job is?

If this is a frequent interface we normally switch of logging because it does consume memory. So you need to take that into account. So if you have enough space and the system is running fine now. My guess is it wont make that big of a difference. But I dont know your landscape. It is difficult to say what the impact will be.

Regards,

Jannus Botha

[robert_warde4 · Accepted solution]

Hi

We have enabled this in our D, Q and R systems but yet to apply to production. Hopefully, this will be performed next month.

Messages are deleted after 7 days unless they fail and then we retain them for 31 days. We need to keep messages for a week as although the message may have been successfully delivered it may be that the business has questions about the actual data sent. We could switch of logging but then we are running blind.