Question
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Cognizant Technology Solutions
US
Last activity: 15 Apr 2021 15:17 EDT
Issue with Pega Log Viewer tool
I downloaded the Pega Log viewer 3.1 from GitHub. When I try to upload the alert logs, its asking for log4j pattern (Attached screenshot). I have tried every possible combination. But nothing is working.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Updated: 5 Apr 2020 11:30 EDT
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/2025-01/80f151c6-644b-4685-92c1-375e470fc75b.jpeg?itok=MdTVYRQw)
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/2025-01/80f151c6-644b-4685-92c1-375e470fc75b.jpeg?itok=MdTVYRQw)
Pegasystems Inc.
US
Hi,
As per the release notes on https://github.com/pegasystems/pega-logviewer
This tool shows the log file line/entries in a table format. The columns are marked based on the log pattern. The log pattern used are the OOTB ones from prlogging.xml -> PEGA appender or prlog4j2.xml -> PEGA appender on 8.x versions.
In case there are updates to PEGA appender pattern. In case the tool can't recognize the pattern automatically, it will present a dialog to enter the pattern, so you might be required to get a customised pattern from prlogging or prlog4j2.xml (8.x) files.
P.S:- I have experienced this issue multiple times with client's PegaRULES log file esp if the log file is altered/trimmed for data masking OR when they change their appender configuration in log4j xml
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Cognizant Technology Solutions
US
Hi Harish,
Thank you for your reply. I got hold of the prlog4j2.xml, and I found the below pattern for the alert log. But if I give %m%n in the Log4j Pattern field, is still not accepting. Is there any generic pattern which I need to provide. I have tried every possible value, but nothing is working. Should I give any quotes are something while inputting the value.
<PatternLayout>
<Pattern>%m%n</Pattern>
</PatternLayout>
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/1689970000/0d7d463c-332b-4922-a5a7-63bcd2fa82de.png?itok=pcSOjeUi)
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/1689970000/0d7d463c-332b-4922-a5a7-63bcd2fa82de.png?itok=pcSOjeUi)
Pegasystems Inc.
GB
Hi,
Unfortunately, I am unable to open the attached jpg. Can you please check
1. if the filename has "ALERT" in it.
2. can you post first 2 lines of alert. (please do anonymize).
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Cognizant Technology Solutions
US
Hi,
Yes. I am sure I am trying to upload the Alert log file. My application is hosted on Pega cloud. Downloaded the log files from 'My Pega Cloud' in the support portal.
Please find below the 2 lines. I took this from the log excerpt which is shown in the Pop up while uploading the log file.
Also I have reattached the screenshot to this post.
Hi,
Yes. I am sure I am trying to upload the Alert log file. My application is hosted on Pega cloud. Downloaded the log files from 'My Pega Cloud' in the support portal.
Please find below the 2 lines. I took this from the log excerpt which is shown in the Pop up while uploading the log file.
Also I have reattached the screenshot to this post.
2020-04-09 02:08:41,073 GMT*8*PEGA0020*1326*1000*util-i-00360661a7295734f*NA*NA*BG4EKJLA8IUQYA3C7V19NWU9RLQX3JU47A*System*PegaSample*PegaAESRemote:8*753454fcd79e9e1301c6f7e1c42710d8*N*1*BG4EKJLA8IUQYA3C7V19NWU9RLQX3JU47A*21*PegaRULES-Batch-96*STANDARD*com.pega.pegarules.session.internal.mgmt.Executable*NA*PegaAESRemote-Interface-DBStats.PushDBStats*Rule-Obj-Activity:PushDBStats*@BASECLASS PXCALLDATATRANSFORM #20180713T132634.566 GMT Step: 1 Circum: 0*NA*****pxConnectElapsed=1.33;pxTotalReqCPU=0.02;pxRunModelCount=1;pxRulesUsed=4;pxDeclarativePageLoadElapsed=0.00;pxDeclarativePageLoadCount=1;pxConnectClientResponseElapsed=1.32;pxRulesExecuted=4;pxOtherCount=8;pxTotalReqTime=1.33;pxActivityCount=3;pxAlertCount=1;pxOtherFromCacheCount=8;*Rule-Connect-REST*NA*Rule-Connect-REST*NA*doActivity Rule-Obj-Activity:Invoke;Connect-REST;RULE-OBJ-ACTIVITY PEGAAESREMOTE-INTERFACE-DBSTATS PUSHDBSTATS #20190218T054856.248 GMT Step: 14 Circum: 0;doActivity Rule-Obj-Activity:PushDBStats;initial Executable;0 additional frames in stack;*SkipThisRun=[removed];pyQueryStringParameters=[removed];pyRequestParameters=[removed];pyRequestDataList=[removed];pyRequestData=[removed];EndPointURL=[removed];pyResourceParameters=[removed];pyHTTPStatusLine=[removed];Operation=[removed];version=[removed];pzMaxRecords=[removed];pyQueueClass=[removed];pyRequestHeaders=[removed];pzResponseHeaderMap=[removed];QueueNumber=[removed];pyResourcePathParameters=[removed];pyStatusVal=[removed];pyStatusMsg=[removed];pyObjName=[removed];Parameter=[removed];skipBody=[removed];pyHTTPResponseCode=[removed];MethodName=[removed];LockString=[removed];*RULE-CONNECT-REST PEGAAESREMOTE-INTERFACE-DBSTATS PUSHDBSTATS #20190218T054856.123 GMT has exceeded the threshold of 1,000 ms: 1,326 ms;pxConnectOutMapReqElapsed=0;pxConnectClientResponseElapsed=1323;pxConnectInMapReqElapsed=0;*
2020-04-09 02:38:57,353 GMT*8*PEGA0005*1625*500*util-i-00360661a7295734f*NA*NA*BTUYARDRCL51SJ7R775T52UVF652OHNM7A*NA*PegaSample*null*4d8a7acc99a8f6053e49843f465efe7b*N*0*BTUYARDRCL51SJ7R775T52UVF652OHNM7A*22*DataFlow-Service-PickingupRun-pyBatchIndexClassesProcessor:29, Access group: [PRPC:AsyncProcessor], PartitionsEQUALS[13]*STANDARD*com.pega.pegarules.data.internal.store.DataStorePreparedStatement*NA*NA*NA*NA*NA*****NA*NA*NA*NA*NA*;initial Executable;0 additional frames in stack;*BatchSize=[removed];pyEventStrategyStorePartitionCount=[removed];pyEventStrategyForceExpire=[removed];pyEventStrategyStorePartitionScheme=[removed];KeyValueStoreFactory=[removed];pyEventStrategyStorageSchemeKey=[removed];PartitioningFeature=[removed];RunId=[removed];pyCacheSize=[removed];*Database operation took more than the threshold of 500 ms: 1,625 ms SQL: UPDATE pegadata.pr_data_decision_df_part "PC0" SET "pxlastids" = ? ,"pxrecordsprocessed" = ? ,"pxupdatedatetime" = ? WHERE ( "PC0"."pxworkid" = ? AND "PC0"."pxvalues" = ? )*
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Cognizant Technology Solutions
US
Hi,
Any suggestions based on the alert snippet.
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/1689970000/0d7d463c-332b-4922-a5a7-63bcd2fa82de.png?itok=pcSOjeUi)
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/1689970000/0d7d463c-332b-4922-a5a7-63bcd2fa82de.png?itok=pcSOjeUi)
Pegasystems Inc.
GB
I suspect that this is issue with newer Alert version (v8) .
2020-04-09 02:38:57,353 GMT*8*PEGA0005
I tried locally, a different error is thrown, but the change in pattern of alert fields is the underlying issue.
I am preparing next version of logviewer which will address this, along with other features. unfortunately didnt had a chance to commit those yet.
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Cognizant Technology Solutions
US
Thank you for your prompt response. Will wait for the next version of Log Viewer.
Any approximate timeline on when it will be released ?
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/1689984000/f70a88ed-8ec0-4b37-b457-b343b0aa0d98.png?itok=v_6Z8Vin)
![](https://accounts.pega.com/sites/default/files/styles/user_image/public/1689984000/f70a88ed-8ec0-4b37-b457-b343b0aa0d98.png?itok=v_6Z8Vin)
Texas District & County Retirement Systems
US
@ManuVargheseDo you know when can we expect the next update ?