Question
Anthem
US
Last activity: 15 Sep 2021 12:03 EDT
pr_log_reportstats | PEGA0005 Long Running SQL Query.
Hello Everyone,
Below mentioned SQL query related to Log-ReportStatistics seems to be triggered on frequent basis and running long and slowing down the application. Any idea about this functionality triggering this query alongside steps to remediate the same ? Thank you.
Hello Everyone,
Below mentioned SQL query related to Log-ReportStatistics seems to be triggered on frequent basis and running long and slowing down the application. Any idea about this functionality triggering this query alongside steps to remediate the same ? Thank you.
2021-09-07 04:38:45,642 GMT*8*PEGA0005*1374882*500*JVM_NAME*NA*NA*BYZCSV2FQWYP1QD3YIYQU1EBOZXLJ4A14A*USER_ID*XXXX-FW-CSFW-Work*XXXXCSNCCSuper:01.01.01*4220ffbeae23bed3424db18ef235a445*N*1*BYZCSV2FQWYP1QD3YIYQU1EBOZXLJ4A14A*6500*PegaRULES-Batch-5*STANDARD*com.pega.pegarules.data.internal.store.DataStorePreparedStatement*NA*Log-ReportStatistics.pzSaveReportStatUsage*Rule-Obj-Activity:InitialProfileSetup*LOG-REPORTSTATISTICS PZSAVEREPORTSTATUSAGE #20180713T132648.074 GMT Step: 1 Circum: 0*NA*****pxInteractions=1;pxRuleCount=1;pxTotalReqCPU=0.02;pxRulesUsed=18;pxRunWhenCount=8;pxRulesExecuted=18;pxRuleFromCacheCount=1;pxOtherIOElapsed=1,374.88;pxTotalReqTime=1,374.84;pxActivityCount=10;pxOtherIOCount=1;pxAlertCount=1;pxOtherFromCacheCount=1;*NA*NA*NA*NA*java;RULE-OBJ-ACTIVITY LOG-REPORTSTATISTICS PZSAVEREPORTSTATUSAGE #20180713T132648.074 GMT Step: 1 Circum: 0;doActivity Rule-Obj-Activity:pzSaveReportStatUsage;initial Executable;0 additional frames in stack;*NA*Database update took more than the threshold of 500 ms: 1,374,882 ms SQL: INSERT INTO dbo.pr_log_reportstats (pzInsKey , pxCommitDateTime , "TerminationReason" , "pxCreateDateTime" , "pxCreateSystemID" , "pxErrorCount" , "pxInsName" , "pxModeOfExecution" , "pxObjClass" , "pxReportExecutionCount" , "pxReportInsKey" , "pxReportOperator" , "pxRowsRetrieved" , "pxSaveDateTime" , "pxSessionId" , "pxTotalElapsedTime" , "pyClassName" , "pyStreamName") VALUES (? , CURRENT_TIMESTAMP , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?) inserts: <LOG-REPORTSTATISTICS HZJM4QZB37J6FPLPF2TK5FA1ZN5U2XWKHA!JVM_NAME!RULE-OBJ-REPORT-DEFINITION ASSIGN-WORKLIST PYUSERWORKLIST #20210802T183120.602 GMT!EMBEDDED!20210907T041550.758 GMT> <<null>> <2021-09-07 00:15:50.758> <JVM_NAME> <0> <HZJM4QZB37J6FPLPF2TK5FA1ZN5U2XWKHA!JVM_NAME!RULE-OBJ-REPORT-DEFINITION ASSIGN-WORKLIST PYUSERWORKLIST #20210802T183120.602 GMT!EMBEDDED!20210907T041550.758 GMT> <embedded> <Log-ReportStatistics> <1> <RULE-OBJ-REPORT-DEFINITION ASSIGN-WORKLIST PYUSERWORKLIST #20210802T183120.602 GMT> <USER_ID> <10> <2021-09-07 00:15:50.758> <HZJM4QZB37J6FPLPF2TK5FA1ZN5U2XWKHA> <264> <Assign-Worklist> <pyUserWorkList> *
Navy Federal Credit Union
US
@PradeepPydi This is triggered from an background agent to log the time taken by report definition to execute. This is done for every report definition run.
You can disable this by setting the DSS reporting/enablestatistics in Pega-RulesEngine ruleset to false
Anthem
US
@Devang Do you recommend disabling the following related DSS reporting/enablestatisticsForEmbeddedReports as well ?
Please also suggest the consequences of disabling both ?
Thanks in advance.
Navy Federal Credit Union
US
@PradeepPydi Only consequence is that Pega(agent) will not write statistics to DB. If you do not need this data then you can safely disable them