Download the PHP package danilovl/log-viewer-bundle without Composer

LogViewerBundle

This Symfony bundle provides a user-friendly interface and API for viewing application logs (Monolog). It supports log reading through standard PHP methods as well as a high-performance Go-based parser.

Features

• Advanced Search: Support for regular expressions (Regex), case-sensitivity toggles, and search term highlighting in the search bar.
• File Reader: "Nano-like" log file viewer that loads content incrementally as you scroll, allowing you to read files of any size without browser performance issues.
• Jump to Line: Quickly navigate to any specific line in the log file within the File Reader.
• Line Numbers: Each log entry is now associated with its exact line number in the source file, making it easy to reference and find in the original log.
• Global Search: Search across multiple log files at once from a dedicated page with combined and time-sorted results.
• Regex Templates: Predefined collection of popular regular expressions for common log patterns, with specific implementations for PHP/Symfony and Go.
• Live Multi-source View: Select multiple log files in the Live Log view via a modal to monitor them simultaneously in a single real-time stream.
• Zen Mode: Fullscreen distraction-free mode that hides the sidebar and header, perfect for monitoring logs on a dedicated display.
• Bookmarks: Quickly mark specific log entries with a "star" and filter to see only your bookmarked items. Bookmarks are persisted in your browser's local storage.
• Modern Dashboard: Vue 3 based Single Page Application (SPA) for a smooth user experience.
• Log Viewing: Advanced filtering, search (including Regex and Case-sensitivity), and pagination for historical logs.
• Live Log View: Real-time log streaming with automatic updates and level-based filtering.
• Multiple Parsers: Support for Monolog, Nginx, Apache, PHP, Syslog, and more.
• High Performance: Optional Go-based parser for extremely fast processing of large log files.
• Log Statistics: Detailed charts and metrics (by level, channel, timeline) with interactive range selection powered by Google Charts.
• View in Reader: Open any log entry directly in the File Reader from the Dashboard, Logs, Live, or Global Search views to see its surrounding context.
• Auto-Refresh: Configurable real-time updates for dashboard and individual log views.
• Font Size Control: Adjust the font size in the File Reader dynamically for better readability.
• AI-Powered Analysis: Quick "Ask AI" button for error logs, supporting ChatGPT, Perplexity, Gemini, Claude, and more.
• Dark & Light Modes: Full support for dark and light themes, respecting system preferences or manual toggle.
• Multilingual: Supports 10+ languages (English, Russian, Chinese, Hindi, Spanish, French, Arabic, Portuguese, Japanese, German).
• Remote Logs: View logs from remote servers via SSH/SFTP.
• REST API: Full-featured API for integration and custom dashboard development.
• Log Notifications: Real-time notifications for log entries matching specific rules via Symfony Notifier.
• File Management: Ability to download and delete log files directly from the dashboard.
• Ignore Files: Flexible exclusion of specific log files or directories.

Screenshots

Explore the user interface and features of the Log Viewer:

Requirements

• PHP 8.5+
• Symfony 8.0+

Installation

1. Install the package via Composer:

2. Register the bundle in config/bundles.php (if not done automatically):

3. Run the following command to install the bundle assets:

4. Include the routes in config/routes.yaml:

Configuration

Create a configuration file config/packages/danilovl_log_viewer.yaml.

1. Full Configuration Reference

This example shows all available configuration keys with their structure and default values.

2. Real-world Configuration Example

A practical example for a typical production environment.

Note: for ssh and sftp types, the ssh2 PHP extension is required.

Log Notifications (Watcher)

To enable real-time notifications for new log entries matching your rules, you need to run the watcher command in the background.

• --interval (-i): Polling interval in seconds (default: 5).
• --limit (-l): Maximum number of new entries to process per file in each poll (default: 100).

The watcher uses the symfony/notifier component. Make sure you have configured your Notifier transports in your Symfony application.

Configuring Notifier Channels

To use the channels defined in your configuration, you need to configure the corresponding transports in your Symfony application's config/packages/framework.yaml.

1. Slack Example

Install the Slack notifier: composer require symfony/slack-notifier

Channel in rule: chat/slack

2. Telegram Example

Install the Telegram notifier: composer require symfony/telegram-notifier

Channel in rule: chat/telegram

3. Email Example

Make sure the mailer component is configured:

Note: For email notifications to work through the Notifier, you might also need to set up a channel_policy or ensure your AdminNotification logic (if customized) supports it. By default, the bundle sends a standard Notification with the specified channels.

Refer to the official Symfony Notifier documentation for detailed transport configuration (DSN) for each provider.

Built-in Parsers

The following parsers are available by default:

• monolog - Standard Monolog format (usually auto-detected for Symfony logs).
• json - Logs in JSON format (one object per line).
• nginx - Nginx access logs.
• nginx_error - Nginx error logs.
• apache - Apache access logs.
• php - PHP error logs.
• mysql - MySQL error logs.
• syslog - Traditional Syslog.
• syslog-modern - Modern Syslog format.
• doctrine - Doctrine DBAL logs.
• access - Generic access logs.
• supervisord - Supervisord logs.

Regex Templates

The bundle includes a curated list of popular regular expression templates to help you find common issues quickly. Each template provides optimized patterns for both PHP and Go (if the Go parser is enabled).

Available template categories:

• Application: Symfony Deprecation, Symfony Security, Symfony Messenger, Doctrine Query Time, PHP Syntax Error, PHP Warning, PHP Notice, Twig Template Error.
• Errors: Exception, Fatal Error, SQL Error, Stack Trace, Stack Frame.
• Network: IPv4, IPv6, IP with Port, URL, Email, HTTP Referrer, User Agent, Upstream Address.
• HTTP/Web: HTTP Method, Status Error, SQL Query, Framework Route, HTTP Version.
• System: Process ID (PID), Supervisor Status, Cron Task, Kernel Message, Log Channel, Memory Usage, Runtime Version.
• Identifiers: Request ID, User ID, UUID.
• Time/Date: ISO 8601, Brackets, Unix Timestamp, Time Duration.
• General: JSON Block, Quoted String, File Path.
• Sensitive: Credit Card (Masked), Phone Number.

You can select these templates from the dropdown menu in the search bar.

Usage (Dashboard)

After installation and route configuration, the dashboard will be available at: /danilovl/log-viewer

User Interface Features

• Modern SPA: The dashboard is a Single Page Application built with Vue 3 and Pinia for fast, reactive navigation.
• Theme Support: Includes both Light and Dark themes. The theme can be toggled manually or follow system preferences.
• Localization: Supported languages include English, Russian, Chinese, Hindi, Spanish, French, Arabic, Portuguese, Japanese, and German. You can switch the language directly in the UI.
• Interactive Statistics: Real-time charts for log level distribution, channels, and error trends over time. Includes an interactive timeline selector (zoom) to focus on specific periods.
• Live View: Dedicated page for watching incoming logs in real-time, perfect for debugging active issues. Features color-coded status for new entries and level filtering.
• File Reader (Nano-like): An advanced viewer for reading raw log files line-by-line with infinite scrolling. Supports jumping to specific lines and adjustable font sizes. Perfect for examining the full context of an error.
• Ask AI: When viewing error logs, use the "Ask AI" button to quickly analyze the error with your favorite AI chat. You can review and edit the prompt before sending it to ensure no sensitive data is shared. The list of AI chats and their query patterns is fully configurable.
• Auto-Refresh: Stay up to date with incoming logs and dashboard statistics using the built-in auto-refresh feature with countdown indicators.

Development (Assets)

The bundle's assets are pre-built and included in the package. If you want to customize the frontend:

1. Install dependencies:

2. Build for production:

Cache Clear

To clear the bundle cache (including log statistics and parser detection), run the following command:

API Endpoints

All API endpoints are prefixed with /danilovl/log-viewer/api.

1. Configuration

GET /config Returns the current bundle configuration (available levels, channels, etc.).

2. Folder Structure

GET /structure Returns a hierarchical structure of folders and log files.

GET /folders Returns a flat list of folders containing log files with their total count. Response: { "folders": [...], "totalCount": 0 }

3. Log Entries

GET /entries Returns log entries for a specific source with pagination. Query parameters:

• sourceId (string, required): The Source ID to view.
• limit (int): Number of entries (default: 50).
• cursor (string): Cursor for pagination.
• offset (int): Numeric offset.
• sortDir (desc|asc): Sorting direction.
• level (string): Filter by log level.
• channel (string): Filter by channel.
• search (string): Search text.
• searchRegex (bool): Enable regex search.
• searchCaseSensitive (bool): Enable case-sensitive search.
• dateFrom (string): Filter by start date.
• dateTo (string): Filter by end date.

GET /file-content Returns raw file content with pagination and line jumping. Query parameters:

• sourceId (string, required): The Source ID.
• limit (int): Number of lines (default: 100).
• offset (int): Numeric offset (starting line).
• line (int): Jump to a specific line number.

GET /entries/new Returns only new log entries across specified sources (used for real-time updates). Query parameters:

• levels (string): Comma-separated list of log levels to filter (optional).
• sourceIds (string): Comma-separated list of Source IDs (optional).

GET /global-search Returns log entries for multiple sources with combined sorting. Query parameters:

• sourceId (string, required): Comma-separated list of Source IDs.
• limit (int): Number of entries.
• offset (int): Numeric offset.
• sortDir (desc|asc): Sorting direction.
• level (string): Filter by log level.
• channel (string): Filter by channel.
• search (string): Search text.
• searchRegex (bool): Enable regex search.
• searchCaseSensitive (bool): Enable case-sensitive search.

GET /entries-count Returns the total count of entries for the given filters. Query parameters:

• sourceId (string, required): The Source ID.
• level (string): Filter by log level.
• channel (string): Filter by channel.
• search (string): Search text.
• searchRegex (bool): Enable regex search.
• searchCaseSensitive (bool): Enable case-sensitive search.
• dateFrom (string): Filter by start date.
• dateTo (string): Filter by end date.

Response: { "totalCount": 0 }

4. Statistics

GET /stats Returns statistics for a specific file (total count, distribution by levels and channels). Query parameters:

• sourceId (string, required): The Source ID.
• level (string): Filter by log level.
• channel (string): Filter by channel.
• search (string): Search text.
• searchRegex (bool): Enable regex search.
• searchCaseSensitive (bool): Enable case-sensitive search.
• dateFrom (string): Filter by start date.
• dateTo (string): Filter by end date.
• timelineFormat (string): Format for timeline (minute, hour, day).

GET /dashboard-stats Summary statistics across all sources for the dashboard. Query parameters:

• timelineFormat (string): Format for timeline (minute, hour, day).

5. File Management

DELETE /delete Deletes a specific log file. Query parameters:

• sourceId (string, required): The Source ID.

GET /download Downloads a specific log file. Query parameters:

• sourceId (string, required): The Source ID.

Events

The bundle provides several events that allow you to customize its behavior without modifying the core logic. You can use these events to filter logs, change file permissions, or modify log entries.

1. LogViewerDataEvent

Dispatched when collecting data for both folder structure and flat file list.

• Event Class: Danilovl\LogViewerBundle\Event\LogViewerDataEvent
• Properties:
  • structure (list<LogViewerFolderStructure>): The hierarchical structure of log sources.
• Use case: Filter out specific folders or files from the list or modify their properties (like canDelete, canDownload) globally for the entire application. Modifying the structure property directly affects what is shown on the dashboard and sidebar.

2. LogViewerEntriesEvent

Dispatched after fetching log entries for a specific file, but before they are sent to the frontend.

• Event Class: Danilovl\LogViewerBundle\Event\LogViewerEntriesEvent
• Use case: Modify log entries (e.g., anonymize sensitive data or add extra metadata).

3. LogViewerDownloadEvent & LogViewerDeleteEvent

Dispatched before downloading or deleting a log file.

• Event Classes:
  • Danilovl\LogViewerBundle\Event\LogViewerDownloadEvent
  • Danilovl\LogViewerBundle\Event\LogViewerDeleteEvent
• Use case: Stop the propagation of the event to block the action based on custom security rules.

Example of an Event Subscriber:

Custom Log Parsers

You can create your own log parser if your logs are not in the standard Monolog format.

1. Create a Parser Class

Implement the Danilovl\LogViewerBundle\Interfaces\LogInterfaceParser:

2. Register the Parser

If you use standard Symfony autowiring and autoconfiguration, your parser will be automatically registered and tagged with danilovl.log_viewer.parser.

3. Use the Parser in Configuration

Update your danilovl_log_viewer.yaml:

Or set it as the default:

License

The LogViewerBundle is open-sourced software licensed under the MIT license.