For the complete documentation index, see llms.txt. This page is also available as Markdown.

Log Manager

Log Manager

View Log Manager in the section Tools enables management of automations responsible for deleting logs older than a specified period. These automations ensure smooth system operation, space optimization, and regular cleanup of unnecessary data. This feature allows users to monitor and edit automation schedules and manually launch cleanup processes.

Automation table view

The table presents all configured automations responsible for log retention across different areas of the system.

Table columns:

  • Name - Unique name of the automatic log cleanup task.

  • Operation status -Current state of the task (e.g., idle, running).

  • Last result - Result of the last task execution (e.g., success, error).

  • Interval - Time unit defining how often the task is run (e.g., day).

  • Retention time [days] - Number of days for which log data is retained before deletion.

  • Last cleanup - Date and time of the last cleanup process execution.

  • Next cleanup - Scheduled date and time of the next task execution.

  • First cleanup - Date and time of the first task execution since its creation.

  • Active - Indicates whether the task is currently enabled (Yes/No).

  • Description - Brief description of the task function, including the type of data subject to cleanup.

User actions

Each table row contains a set of actions available to the user:

  • Action button (status toggle) – Enables or disables the automation.

  • PLAY icon – Manually starts the automation outside the schedule.

  • Pencil icon (edit) – Opens the menu for editing automation parameters.

Automation editing

Clicking the pencil icon opens the automation configuration side menu.

Editable items

  • Status – Option to activate/deactivate the automation.

  • Frequency – Defines how often the automation is to be run (e.g., day, week, month).

  • Retention time – Number of days logs are retained. Data older than the specified period will be deleted.

  • Start – Activation date of the automation set using the calendar.

Buttons

  • Save changes– Confirms changes to the automation configuration.

  • Cancel – Cancels changes without saving.

Automations and their use cases

Each automation is responsible for a different area of system logs.

AutoDELETETracking

Automation responsible for deleting tracking data older than the specified number of days.

7

Year

AutoDELETEWebTracking

Automation responsible for deleting web activity tracking data older than the specified number of days.

30

Day

AutoDELETEEventlogHistory

Automation responsible for deleting system event history older than the specified number of days.

14

Day

AutoDELETEPerfMon

Automation responsible for deleting system performance monitoring data older than the specified number of days.

7

Day

AutoDELETENetTrafficMon

Automation responsible for deleting network traffic data older than the specified number of days.

7

Day

AutoDELETEHostsGuiAppMon

Automation responsible for deleting GUI application monitoring data older than the specified number of days.

60

Day

AutoDELETELoginHistory

Automation responsible for deleting user login history older than the specified number of days.

30

Day

AutoDELETEScreenshots

Deletes screenshots older than the specified number of days from the system.

Applies to screenshots captured automatically at the moment of a DLP policy violation, if this option has been enabled in the rule configuration.

30

Day

AutoDELETEScreenVideos

Deletes screen recordings older than the specified number of days from the system.

Applies to video recordings captured automatically after a DLP policy violation, if recording has been enabled in the rule configuration.

30

Day

Summary

View The Log Manager offers advanced capabilities for managing log data retention in the eAuditor system. Through precise configuration of schedules and retention periods, users can optimize system performance and manage disk space. The automation feature minimizes the need for manual intervention, ensuring efficient system operation.

Last updated

Was this helpful?