The Logging system settings allow you to configure the Micetro log, including the logging level and the number of days after which log messages should be deleted, as well as whether a lease history for DHCP servers should be collected.
Micetro log
Configure the Micetro log by configuring the following system settings:
- Logging level for Micetro Central (0–7)
- Determines the level of detail to log when logging the output of Micetro Central to a file. For more information about logging levels, refer to Log levels.
- Log file for Micetro Central
- Specify the path and name of the log file to use when you want to log the output of Micetro Central to a file.
- Purge log message after (# of days)
- Enter the number of days the logs should be kept before they are deleted.
- Log extra information when address collection is triggered
- When selected, information about the start and duration of the address collection is written in the Micetro log file.
- Maximum log file size in MB
- Enter the desired maximum log file size in MB. When the maximum file size is reached, the current file is rotated and stored with a .1 ending, and previously rotated files are renamed to have a .2 ending, etc.
Lease history
You can set Micetro to start collecting lease history for DHCP servers, either DHCPv4, DHCPv6, or both. By viewing the DHCP lease history, you can quickly identify any potential issues or conflicts.
Select and set the following system settings as appropriate:
- Collect lease history for DHCPv4 servers
- Select the checkbox to enable lease history collection for DHCPv4 servers.
- Collect lease history for DHCPv6 servers
- Select the checkbox to enable lease history collection for DHCPv6 servers.
- Purge lease history after (# of days)
- Enter the number of days to retain the lease history before it is deleted.
- Flush lease history to file before purging
- If you want to save the history to a comma-separated text file before it's deleted, enter a name for the file in the provided field.