Log Files

Log Files Functionality Overview

The Log Files feature in the Mideye Server interface provides a convenient and efficient way for administrators to access and review log files directly within the web interface, eliminating the need to log into the server’s file system. This functionality retrieves log files from the /opt/mideyeserver6/log directory and displays them in the browser, offering comprehensive visibility into server activity and system operations.

Windows: C:\Program Files (x86)\Mideye Server 6\log\

Key Features

1. Log File Selection Dropdown

   • Easy Access:
     Users can select from a list of available log files through a dropdown menu, enabling quick access to different log types.
   • Available Log Types:
     • mideyeserver.log: The primary log file containing general logs related to Mideye Server operations.
     • mideyeserver.error.log: Dedicated error log file capturing errors and warnings for debugging and monitoring purposes.
     • Rotated Log Files:
       Access historical logs such as mideyeserver.log.1, mideyeserver.log.2, etc., allowing users to review previous system activity and incidents.

2. Log File Content Display

   • Real-Time Viewing:
     The content of the selected log file is displayed in the main view area, providing a real-time look at the log data.
   • Structured Format:
     Logs are presented in a structured format, including:
     • Timestamps: Precise date and time of each log entry in UTC, offering chronological insight into system activities.
     • Log Level Indicators: Each entry displays its log level (e.g., INFO, WARN, ERROR), helping administrators quickly identify critical messages.
     • Thread Information: Detailed thread data such as thread IDs, useful for monitoring and debugging multi-threaded applications.
     • Messages: The core content of each log entry, capturing specific events, requests, responses, errors, and other system behaviors.

3. Export Functionality

   • Log Export:
     Administrators can export the displayed logs to a LOG file for offline analysis, archiving, or sharing with team members. This feature enhances flexibility in log management and reporting.

4. Real-Time Display

   • Immediate Monitoring:
     As logs are retrieved from the /opt/mideyeserver6/log directory and displayed in the browser, administrators can monitor server activities in near real-time by refreshing the page.
   • Use Cases:
   • Troubleshooting and Debugging: Quickly identify and resolve issues as they occur.
   • System Health Monitoring: Continuously monitor the operational status of the server without needing shell access.

Technical Benefits

• Centralized Log Viewing:
  All relevant Mideye Server logs can be accessed through the browser, simplifying the log review process and reducing the need for direct server access.

• Improved Troubleshooting:
  With quick access to different log files, administrators can identify and diagnose issues faster, leveraging timestamped log entries and error details.

• Secure and Controlled Access:
  Displaying logs through a browser-based interface ensures that access to server logs can be restricted and monitored through web access controls, enhancing security compared to direct server access.

• Historical Log Review:
  Rotated log files offer the ability to review past logs, supporting audits, trend analysis, and incident investigations.

Example Use Cases

• Monitoring System Events:
  View logs to track requests and responses handled by the Mideye Server, including RADIUS packet handling and client authentication results.

• Debugging Errors:
  Use mideyeserver.error.log to identify and address issues by examining detailed error messages and related context.

• Tracking SSL Certificate Expirations:
  Log entries can include warnings or informational messages regarding SSL certificate expiration or renewal, which are critical for maintaining secure communication.