Log

In the Log page, users can configure settings related to logging. Logging is the process of recording events, actions, or messages that occur within the Admin Console. Logs are useful for debugging, monitoring, and analyzing the behavior of the application. By clicking on the “Log” button, users will be navigated to the “Log Settings” and “Log Download” window.

Log Settings

• Log Type: Logs can be categorized in various ways based on the nature of the information they capture. Following are the common types of logs:
  • EventLog: These logs capture events or incidents that occur within a system. Examples include login attempts, system startups and shutdowns, security events, and application-specific events.
  • File: File logs record activities related to file and directory operations. This includes creating, modifying, deleting files, and other file system-level events.
• MinLevel: In this field, users will be able to specify the minimum log level that should be recorded or displayed. Log levels are used to categorize log messages based on their severity or importance. Log messages with a severity level equal to or higher than the specified minimum level will be captured or displayed, while messages with a lower severity will be ignored.
  • Trace: The lowest level of severity, typically used for very detailed debugging information. Messages at this level provide fine-grained details about the application’s behavior.
  • Debug: Used for debugging information. Debug messages are slightly less detailed than trace messages but are still intended for debugging and development purposes.
  • Error: Indicates that an error or exception occurred during the application’s execution. Error messages are used to capture and report problems that need immediate attention.
  • Info: Informational messages that indicate the normal operation of the application. These messages are typically used to capture important events or milestones in the application’s execution.
  • Warn: Warnings represent potential issues or non-critical problems. They indicate that something unexpected happened or that there may be a problem that should be investigated.
  • Fatal: The most severe log level, used to indicate critical errors that usually lead to the application’s termination. Fatal messages are reserved for the most severe issues.

Log Download

• Event Log Name: This field refers to the specific log or set of logs that the user would want to download. In a system or application, there could be multiple logs capturing different types of events or activities (e.g., security logs, application logs, system logs). The “Event Log Name” allows the user to select the specific log or category of logs that they are interested in.
• Start Date: This field indicates the beginning date and time from which the user would want to include the log entries in the download. It helps the user to narrow down the range of logs they are interested in. Only log entries recorded on or after the specified start date will be included in the Download.
• End Date: Similar to the “Start Date” field, the “End Date” field allows the user to set the date and time up to which they want to include the log entries in the download. Log entries recorded on or before the specified end date will be included.
• Download Path: This field specifies the location or path where the downloaded log file will be saved on the local system. It could be a directory or folder path where the user wants to store the log file. This is the location on the computer where the downloaded logs will be stored for further analysis or archiving
• The “Clear” button will remove all the details filled in the respective fields and the “Download” button will download the file in a “.evtx” file format.