System logs overview and table rotation schedulesIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This article describes the logs available in the System Logs module and their default table rotation schedules. Use these logs to troubleshoot and review transactions and events in your instance. Most tables in the System Logs module use table rotation to manage transient data.Many log tables extend from the System Log [syslog] table.The default rotation for syslog is 7 days × 8 rotations, retaining approximately 42–49 days of data.Localhost and wrapper logs are compressed after 2–3 days and deleted after 21 days. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All supported releases Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } About table rotation Most tables in the System Logs module use table rotation to store transient data for troubleshooting and review. Some tables, such as Table Changes [sys_schema_change], do not use rotation. Many log tables extend from the System Log [syslog] table. The default rotation for syslog is 7 days × 8 rotations. This configuration retains approximately 42–49 days of data before the oldest rotation is removed. The retention period is 42–49 days rather than 56 days because one rotation is kept empty to prepare for the next rotation, and the current rotation may not contain a full 7 days of data depending on when the last rotation occurred. Default rotation schedules The following table lists the rotation schedules for frequently used log tables in a default instance. To access these logs, go to System Logs in the application navigator. Table Schedule Rotations Type Event [ecc_event] Every day 7 Rotation Queue [ecc_queue] Every day 7 Rotation Event [sysevent] Every day 7 Rotation Log [syslog] Every week 8 Rotation Transaction Log [syslog_transaction] Every week 8 Rotation Email [sys_email] Every 30 days 8 Extension Note: The Email [sys_email] table does not include table rotation by default for instances created after the Istanbul release. You should not enable table rotation or extension for sys_email. Node log files Localhost logs and wrapper logs for the node the user is connected to are available in the Node Log File module. The instance compresses past localhost and wrapper logs after 2–3 days for disk space management and deletes them after 21 days. Performance considerations Modifying the default rotation settings can affect instance performance: Increased rotations: Tables may be joined to fetch data if the filter criteria spans multiple rotations. Transactions may time out due to large data volume or exceed the transaction quota rule for UI transactions.Child table inheritance: Tables that extend from syslog inherit rotation changes. Consider the impact on child tables before modifying syslog settings.Reverting changes: The process to revert rotation changes is not straightforward and may require manual intervention and downtime.Disk space: Increased data retention leads to increased disk space usage. General guidelines Test rotation changes thoroughly in a non-production instance before implementing in production.To extend data retention, modify the duration rather than the number of rotations. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Table Rotation Apply Table Rotation System logs information Transaction logs System logs Log history