Table of Contents
π Squirrel Log Viewer
π Overview
The Log Viewer in Squirrel is a powerful diagnostic and auditing tool designed for real-time visibility into system operations. It enables both administrators and support staff to monitor key activities such as:
- Login attempts - Archive and restore actions - System-level processes - Errors and warnings
By providing deep insights into event history, the Log Viewer plays a crucial role in maintaining the integrity and reliability of the Squirrel platform.
π§° Key Features
The Log Viewer interface is intuitive and built for both speed and precision. It includes several tools to help you find, filter, and export log data with ease:
- π Search Logs Use the keyword-based Search Bar to quickly find entries by username, file GUID, or action type (e.g., βarchiveβ, βrestoreβ).
- π Event Type Filtering Narrow results using the Event Filter Dropdown, allowing you to focus on specific categories such as:
- `Info` β General operations and status messages
- `Warnings` β Potential issues that may require attention
- `Errors` β Critical failures or unsuccessful operations
- π Date Picker Select a specific day to view log entries from that date β useful for auditing and time-based troubleshooting.
- βοΈ Pagination Controls Easily navigate through large sets of log data using Previous/Next buttons at the bottom of the table.
- π₯ Export to CSV Export the current log view to a `.csv` file for external analysis, audit reporting, or record keeping.
- π Refresh Logs Click Refresh Logs at any time to load the most recent entries and ensure you're viewing up-to-date activity.
π Log Table Structure
The log entries are displayed in a clean, tabular format with the following columns:
- π Timestamp The exact date and time the event occurred. Crucial for tracking activity sequences or investigating incidents.
- π Event Type Categorizes the event as Info, Warning, or Error. These tags help prioritize what needs attention.
- π Details A descriptive summary of the action taken. Depending on the event, this may include:
- File GUID or Site GUID
- Action performed (archive, restore, login)
- User involved
- Status or outcome
Each entry tells a clear story of what occurred, when, and who initiated it.
πΌ Use Cases
Here are some common scenarios where the Log Viewer proves invaluable:
- Troubleshooting Errors: Filter for `Error` logs to identify failed archive or restore attempts. - Auditing User Activity: Track who restored or archived what β and when. - File History Tracing: Follow the timeline of a specific file by searching its GUID. - System Monitoring: Watch for signs of unusual system activity or high volume actions.
If you need help interpreting logs or exporting them for analysis, please contact [support@smikar.com](mailto:support@smikar.com).