How to Analyze Server Data Using Compact Log Viewer Server logs contain vital information about your application’s health, performance, and security. However, raw log files are often massive and difficult to read. Compact Log Viewer is a lightweight, cross-platform desktop application designed to make searching, filtering, and analyzing structured logs (especially JSON logs produced by frameworks like Serilog) fast and intuitive.
Here is a step-by-step guide to efficiently analyzing your server data using Compact Log Viewer. 1. Setting Up and Loading Your Data
Before you can analyze your data, you need to import your log files into the application.
Download and Install: Grab the latest release of Compact Log Viewer for Windows, macOS, or Linux.
Open Your Log File: Click the Open button or drag and drop your .log, .txt, or .json file directly into the application window.
Automatic Parsing: The tool automatically parses structured JSON logs and displays them in a clean, tabular format, separating timestamps, log levels (Information, Warning, Error), and messages. 2. Filtering by Log Level
When a server crashes or slows down, you need to eliminate the noise and focus on critical events.
Quick Toggles: Use the log level checkboxes at the top of the interface (e.g., Verbose, Debug, Information, Warning, Error, Fatal).
Isolate Errors: Uncheck “Information” and “Debug” to instantly isolate “Error” and “Fatal” logs. This reveals exactly when and where your server encountered failures. 3. Utilizing the Search and Filter Bar
Compact Log Viewer features a powerful search bar that supports both simple text matching and complex property filtering.
Text Search: Type a keyword like Timeout or Database to find all log entries containing that text.
Property Filtering: If your logs are structured (JSON), you can filter by specific properties. For example, typing RequestPath = ‘/api/v1/login’ will only show logs generated by that specific endpoint.
Exclusion Filters: You can exclude noisy logs by using negative operators (e.g., not(SourceContext = ‘Microsoft.AspNetCore’)) to clean up your view. 4. Deep-Diving into Structured Properties
Clicking on any log row expands a detailed view pane, which is where the real analysis happens.
Inspect Event Properties: See all contextual data attached to the log event, such as MachineName, Environment, UserId, or ExecutionTimeMs.
Exception Tracking: If an error occurred, the expanded view will display the full stack trace. This helps you identify the exact line of code that caused the failure. 5. Finding Patterns and Troubleshooting
To turn raw data into actionable insights, use these analytical strategies:
Correlate via Request ID: Look for a RequestId or CorrelationId in the properties of an error log. Paste that ID into the search bar to see the exact sequence of events leading up to the failure.
Identify Performance Bottlenecks: Filter for logs where ElapsedMilliseconds or a similar performance metric exceeds your threshold (e.g., Elapsed > 500) to find slow database queries or API calls.
Monitor Trends: Use the timeline view to see if errors spike at specific times, which can point to scheduled cron jobs, heavy traffic periods, or memory leaks.
To help tailor this guide or troubleshoot further, let me know:
What log framework does your server use? (Serilog, NLog, Log4Net, etc.)
Leave a Reply