Question

2
Replies
100
Views
 Ozgul BATTAL (OzgulB63)
Qnb Finansbank

Qnb Finansbank
TR
OzgulB63 Member since 2020 2 posts
Qnb Finansbank
Posted: October 30, 2020
Last activity: December 19, 2020
Posted: 30 Oct 2020 14:59 EDT
Last activity: 19 Dec 2020 1:12 EST

PEGA-alert & PEGA-rules logs are in different time zones.

Report 
Hi,
Our Pega-ALERT logs and Pega-RULES logs are at the different time zones on the servers.
I learned from the support team that the PEGA-ALERT log is set according to GMT.
Is it possible to set both logs to the same time zone?
I don't see time zone settign for the PEGA-ALERT log in prlog4j2.xml file.
How can i change time zone of PEGA-ALERT log?

Thanks for your help,
Pega Marketing 8.1 System Administration Financial Services System Administrator
Reply
Posted: 6 months ago
Posted: 19 Dec 2020 1:12 EST
Hoyath Singapore (Hoyath)
PEGA
Technical Solutions Engineer
Pegasystems Inc.
IN
Report

Hi @OzgulB63,

In prlog4j2 under Alert category you will notice pattern as %m%n The tricky part is that the timestamp in alert log is included in the message param. 

I.e. %m contains the timestamp and alert details. (Hardcoded GMT) Adding %d to this pattern will result in printing of JVM provided time zone’s timestamp. I.e. %d%m%n will return

2020-12-03 14:40:49,827 2020-12-03 03:40:49,827 GMT*8*PEGA0005*1044*500*….

Timezone gets added twice and need less to mention that the message contains Hardcoded GMT.

There is a way to even fix this but there are certain complications. You can use regex to remove the OOTB GMT timestamp from the log.

Using %d %replace{%m}{[0-9]{1,4}-[0-9]{1,2}-[0-9]{1,2} [0-9]{1,2}:[0-9]{1,2}:[0-9]{1,2},[0-9]{1,3} GMT}{ACT} %n

(This removes the timestamp followed by GMT and replaces it with ACT)

This resolves the problem and will log everything in ACT but the complication is when you want to read/parse this log file using Pega log viewer it assumes that the alert log is in GMT and behaves accordingly. So, I would suggest to let alerts to print in GMT.

 

Reply