Hi Asif. There's no screenshot. We are just accumulating entries in pegadata.pr_log_reportstats.
The logging is handled by another thread, so there is no direct impact on the current thread of processing, but it does create workload for the database server that may impact the scalability of some database-intensive Agent processing we are performing. Because the operation happens in another thread I have been unable to identify in the tracer how it is requested by the current thread.
The logging is performed by activity LOG-REPORTSTATISTICS PZSAVEREPORTSTATUSAGE so presumably there is a Queue-for-Agent somewhere that is invoking this. The activity is Final, Internal so I cannot directly influence it's operation, but if I can find where it is invoked I may be able to add some conditional logic.
***Updated by moderator: Lochan to add note on link***