Log files
Modify the configuration of ESET Endpoint Security logging. You can view the log files with ESET PROTECT On-Prem.
To configure the ESET Endpoint Security remotely:
1.In ESET PROTECT, click Policies > New policy and type a name for the policy.
|
To adjust the settings in an existing policy for ESET Endpoint for macOS (V7+), click the policy you want to change in the list of policies and click Edit > Settings. |
2.Click Settings and select ESET Endpoint for macOS (V7+) from the drop-down menu.
3.Adjust the desired settings.
4.Click Continue > Assign and select the appropriate group of computers.
5.Click Finish.
|
To configure the ESET Endpoint Security locally see application preferences. |
In Tools > Log files, you can configure the following settings:
Minimum logging verbosity
Logging verbosity defines the level of details the log files include.
•Critical warnings – Includes only critical errors (for example, failed to start antivirus protection).
•Errors – Errors such as "Error downloading file" will be recorded in addition to critical warnings.
•Warnings – Critical errors and warning messages will be recorded in addition to errors.
•Informative records – Record informative messages, including successful update messages, plus all records above.
•Diagnostic records – Include information needed to fine-tune the program and all records above.
Automatically delete records older than (days) – Log entries older than the specified number of days will be automatically deleted.
Optimize log files automatically – When engaged, log files will automatically be defragmented if fragmentation percentage is higher than the value specified in the If the number of unused records exceeds (%) field. All empty log entries are removed to improve performance and log processing speed. This improvement can be observed when the logs contain a large number of entries.
Syslog Facility
Syslog facility is a syslog logging parameter used to group similar log messages. For example, daemon logs (which collect logs via syslog facility daemon) can go to ~/log/daemon.log if configured. With the recent switch to systemd and its journal, syslog facility is less important but still can be used for filtering logs.