Question
Ganga
IN
Last activity: 12 Jul 2024 10:54 EDT
Runtime Logs are appending on the same runtimelog.txt
Hi
All the runtime logs are appending on the same runtime log file, how to make it append on the other runtime log files. Any help is appreciated. Thanks,
Ganga
***Edited by Moderator Marije to change type from General to Product, added Product details and Capability tags****
Accepted Solution
Updated: 12 Jul 2024 10:54 EDT
Pegasystems Inc.
US
@GangaR16584219 Log settings are contained within the PegaRuntimeConfig.xml in our current version. If you are using an older version, these instructions will be different.
Logging now uses Log4Net exclusively. In the config file under the log4net node are the log settings. The two settings you should alter are maximumFileSize and maxSizeRollBackups. By default, logs will only grow to 10 MB in size. On DEBUG level, this will fill up quickly. Once a log has reached 10 MB, a new file will be created, and the current one will be renamed with a 1 on the end. The previous log with a 1 on the end will be renamed with a 2 and so on. The one with a 5 will be deleted. When debugging, I suggest changing the max size to "1000MB" or more to increase what you can capture.
@GangaR16584219 Log settings are contained within the PegaRuntimeConfig.xml in our current version. If you are using an older version, these instructions will be different.
Logging now uses Log4Net exclusively. In the config file under the log4net node are the log settings. The two settings you should alter are maximumFileSize and maxSizeRollBackups. By default, logs will only grow to 10 MB in size. On DEBUG level, this will fill up quickly. Once a log has reached 10 MB, a new file will be created, and the current one will be renamed with a 1 on the end. The previous log with a 1 on the end will be renamed with a 2 and so on. The one with a 5 will be deleted. When debugging, I suggest changing the max size to "1000MB" or more to increase what you can capture.
<threshold value="DEBUG" /> <root> <priority value="ALL" /> </root> <logger name="RuntimeLog"> <level value="DEBUG" /> <appender-ref ref="LogFileAppender" /> </logger> <appender name="LogFileAppender" type="log4net.Appender.RollingFileAppender"> <file type="log4net.Util.PatternString" value="%property{path_runtime}\%property{name_runtime}.log" /> <appendToFile value="false" /> <rollingStyle value="Size" /> <maximumFileSize value="1000MB" /> <maxSizeRollBackups value="5" /> <staticLogFileName value="true" /> <preserveLogFileNameExtension value="true" /> <lockingModel type="log4net.Appender.FileAppender+MinimalLock" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%-5level | %property{TimeStamp} | %-3property{TID} | %-3property{State} | %-25.25property{Category} | %-45property{Subcategory} | %message%newline%exception" /> </layout> <threshold value="DEBUG" /> </appender> </log4net>
Pegasystems Inc.
US
@GangaR16584219Are you referring to Pega Robotics Runtime?
Ganga
IN
Accepted Solution
Updated: 12 Jul 2024 10:54 EDT
Pegasystems Inc.
US
@GangaR16584219 Log settings are contained within the PegaRuntimeConfig.xml in our current version. If you are using an older version, these instructions will be different.
Logging now uses Log4Net exclusively. In the config file under the log4net node are the log settings. The two settings you should alter are maximumFileSize and maxSizeRollBackups. By default, logs will only grow to 10 MB in size. On DEBUG level, this will fill up quickly. Once a log has reached 10 MB, a new file will be created, and the current one will be renamed with a 1 on the end. The previous log with a 1 on the end will be renamed with a 2 and so on. The one with a 5 will be deleted. When debugging, I suggest changing the max size to "1000MB" or more to increase what you can capture.
@GangaR16584219 Log settings are contained within the PegaRuntimeConfig.xml in our current version. If you are using an older version, these instructions will be different.
Logging now uses Log4Net exclusively. In the config file under the log4net node are the log settings. The two settings you should alter are maximumFileSize and maxSizeRollBackups. By default, logs will only grow to 10 MB in size. On DEBUG level, this will fill up quickly. Once a log has reached 10 MB, a new file will be created, and the current one will be renamed with a 1 on the end. The previous log with a 1 on the end will be renamed with a 2 and so on. The one with a 5 will be deleted. When debugging, I suggest changing the max size to "1000MB" or more to increase what you can capture.
<threshold value="DEBUG" /> <root> <priority value="ALL" /> </root> <logger name="RuntimeLog"> <level value="DEBUG" /> <appender-ref ref="LogFileAppender" /> </logger> <appender name="LogFileAppender" type="log4net.Appender.RollingFileAppender"> <file type="log4net.Util.PatternString" value="%property{path_runtime}\%property{name_runtime}.log" /> <appendToFile value="false" /> <rollingStyle value="Size" /> <maximumFileSize value="1000MB" /> <maxSizeRollBackups value="5" /> <staticLogFileName value="true" /> <preserveLogFileNameExtension value="true" /> <lockingModel type="log4net.Appender.FileAppender+MinimalLock" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%-5level | %property{TimeStamp} | %-3property{TID} | %-3property{State} | %-25.25property{Category} | %-45property{Subcategory} | %message%newline%exception" /> </layout> <threshold value="DEBUG" /> </appender> </log4net>