Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Changing the time zone in Pega and Alert log entries (Pega 7.2.2 and earlier)

Updated on April 26, 2019

By default, the time stamp in the Alert log appears as a UTC (Coordinated Universal Time) value in Greenwich Mean Time (GMT). You can change the time zone in the Alert log and the Pega log to a different time zone, such as Eastern Standard Time (EST), by editing the prlogging.xml file. The prlogging.xml file controls the location, name, and contents of the Alert log and the Pega log. The logging facility uses Apache Log4j 1.2. For information about changing the time zone in the prlog4j2.xml file, introduced in Pega 7.3, see the Apache Log4j 2 documentation.

This procedure changes only the presentation of the time of log events. One log might contain events from multiple servers in the same or different time zones. The time stamp for each event is based on the system clock of the server that produced the event. In a multinode system, synchronize all the server clocks.
  1. To report alert times based on a time zone other than GMT, edit the prlogging.xml file. On an Apache Tomcat application server, the prlogging.xml file is in the ../prweb/WEB-INF/classes/directory, and a second copy that supports the prdbutl utility servlet is in the ../prdbutl/WEB-INF/classes/directory.
  2. Locate the <appender > element named ALERT:

    <appender name="ALERT"
    class="com.pega.pegarules.priv.util.FileAppenderPega">
    <param name="FileNamePattern" value="'PegaRULES-ALERT-'yyyy-MMM-dd'.log'"/>
    <layout class="com.pega.apache.log4j.PatternLayout">
    <param name="ConversionPattern" value="%m%n"/>
    </layout>
    </appender>

  3. Update the time zone value as needed, for example, for Eastern Standard Time (EST), the value is:

    <appender name="ALERT"
    class="com.pega.pegarules.priv.util.FileAppenderPega">
    <param name="FileNamePattern" value="'PegaRULES-ALERT-'yyyy-MMM-dd'.log'"/>
    <layout class="com.pega.apache.log4j.PatternLayout">
    <param name="ConversionPattern" value="%d{EST} EST -- %m%n"/>
    </layout>
    </appender>

  4. Save the prlogging.xml file.
  5. Redeploy the Pega 7 Platform to make the changes to the prlogging.xml file go into effect the next time the Pega 7 Platform is started on the server node. For more information, refer to the installation guide for your system.
  6. To make a similar change to the Pega log file, update the <appender > element with the name attribute "PEGA".

After saving the changes, each Alert log entry is identified by an EST date and time, for example:

2008-07-11 14:26:02,289 EDT -- 2008-07-11 18:26:02,289
GMT*4*PEGA0001*3486*1000*9268f3d99d7256ffbc938121fa6846ac
*HFF1D02786E84F
91C1376D6A6F6254899*[email protected]*MyFirms-GoalApp*d8262ba66e
19bab32f35e1428a522301*Y*3*3*http-9090-Processor23*com.pega.pegarules.se
rvices.HttpAPI*localhost|127.0.0.1*Stream=NavigationPane*Rule-Obj-Activi
ty:Getfiltered*DATA-ADMIN-OPERATOR-ID GETDEVELOPERPREFERENCESXML
#20060616T145217.546 GMT Step: 3

Review your output carefully. There is no international standard that specifies abbreviations for civil time zones such as CET, EST, and so on, and sometimes the same abbreviation is used for two different time zones. (For input of time zones, PRPC 5.x uses the time zone codes provided by your Java JDK.)

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us