Log Management

the log management screen provides centralized control over system generated log records and their automated cleanup administrators can use this screen to define retention periods for each log type, configure cleanup job schedules, enable or disable individual log management rules, and monitor job execution history primary purpose of this feature is to prevent uncontrolled database growth, maintain system performance, and automate the lifecycle management of log data across the platform log management is designed to handle high volume log tables produced by kron pam components the following log types are supported · user authentication log · radius account log · tacacs account log · activity log · http proxy log · video session log · ocr log each log type can be assigned an independent retention threshold and cleanup schedule, allowing administrators to apply different policies based on the volume and criticality of the data involved before configuring log management rules, the logmanagementscheduler job must be registered and triggered via the job scheduler screen once active, this job performs the following operations at each execution cycle 1 reads all records in the log management configuration table 2 identifies records where the enabled flag is set to active 3 evaluates the start time and time period of each record to determine whether a cleanup job is due for execution note the logmanagementscheduler must be manually triggered at least once after registration to initialize the scheduling cycle to define a new log cleanup schedule, follow the steps below 1\ navigate to the log management screen from the administration menu 2\ click the add new scheduler button to open the rule creation form 3\ in the name field, select the target log type from the dropdown list (e g , activity logs ) 4\ set the day threshold value to define the retention period log records older than the specified number of days will be automatically deleted during each cleanup run for example, setting this value to 2 will remove all records older than two days 5\ set the time period value to define the execution frequency of the cleanup job for example, a value of 2 means the job will run every two hours 6\ use the enable toggle to activate or deactivate the rule only enabled rules are processed by the logmanagementscheduler 7\ specify the start time to define when the first execution of the rule should occur subsequent executions will follow the configured time period interval from this initial timestamp 8\ click save to persist the log management rule field description name identifies the log type to be managed each log type corresponds to a specific database table day threshold defines the retention period in days records older than this value are deleted on each job run time period defines the interval (in hours) at which the cleanup job executes enable activates or deactivates the rule disabled rules are skipped by the scheduler start time sets the initial execution timestamp the scheduler uses this as the reference point for subsequent runs