Issue
The System Logs module provides a variety of logs that you can use to troubleshoot and review transactions and events that took place in the instance.
Information
Most of the tables under the System Logs module are configured to use table rotation. There are exceptions such as Table Changes (sys_schema_change). The tables are meant to store transient data for troubleshooting/review purposes.
Many of the tables listed under System logs module extend from System Logs (syslog) table used for application logging. The default rotation for syslog is set to 7 days x 8 rotations - Data for approximately 42 - 49 days is available before the data in the oldest rotation is removed/truncated (42 - 49 days and not 56 days as one of the rotation will be empty to prep for the next rotation and the data in the current rotation may not contain 7 days data depending on the current datetime and when the last rotation occurred). We believe this configuration is a good a balance between data retention and table management for most customers.
The table below lists the rotation schedule/type for the most frequently used tables in an out of the box instance. You can navigate to the system logs module in your instance to access the related logs. When you click on each link, it will navigate to the corresponding module and you can see the table name in the browser URL.
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
*Please note Email [sys_email] is not included in Table Rotation out-of-the-box if your instance is created after Istanbul release.
Please note that we do not suggest enabling table rotation/extension for sys_email.
Besides the above tables, there are also other logs. For example, the localhost logs and wrapper logs for the node the user is connected to are under the Node log file module. The instance will compress the past localhost and wrapper logs (for disk space management) after 2-3 days and deletes them after 21 days.
Release
All release
Resolution
Please note that there are performance implications if you modify the default number of rotations/duration.
For example, if the number of rotations is increased, tables may be joined to fetch the data if the filter criteria is not datetime bound to a single rotation. The transaction may time out due to large volume of data or if the transaction response time exceeds the transaction quota rule for UI transactions.
As mentioned above, there are tables that extend from syslog. If the rotations/duration of syslog is modified, the changes will be propagated to the child tables. Please consider carefully if you are considering increasing data retention esp via an increase in the number of rotations. The process to revert is not straightforward, may require manual intervention and downtime. Please test and review thoroughly in a subprod instance before implementing in Production. If there is a need to modify the configuration for a longer data retention, we would suggest changing the duration instead of the number of rotations. The increase in data retention may also lead to an increase in disk space usage.
Related Links
Please review the following documentation for more information:
