Meituan-Dianping/Logan
Logan
Logan is a cross-platform mobile logging framework that collects, stores, and uploads client-side logs from iOS, Android, Web, and Flutter environments for centralized debugging and analysis. It provides a complete pipeline from client-side log buffering and file-based local storage through to server-side ingestion and a visual browser for inspecting parsed logs.
The system uses a structured binary protocol to encode log entries with content, type, timestamp, and thread metadata, enabling consistent parsing across platforms. A log receiving server handles uploaded files, while a web-based interface allows searching, scanning, and browsing logs from multiple sessions. The framework also supports viewing local log file metadata on devices and aggregating logs from all sources into a single backend for unified problem analysis.
Features
- Cross-Platform Log Collection - Collecting, storing, and uploading logs from iOS, Android, Web, and Flutter apps for centralized debugging.
- Cross-Platform Logging Frameworks - A cross-platform logging system that collects, stores, and uploads client-side logs from iOS, Android, Web, and Flutter apps for centralized debugging and analysis.
- Structured Log Parsing - Parses client-uploaded logs using a defined protocol that extracts content, type, timestamp, thread name, thread ID, and main-thread flag.
- Log Buffering - Logs are written to local storage in a buffered manner before being uploaded to a remote server for analysis.
- Local File Storage - Logs are persisted as files on the device's file system for later retrieval and upload.
- Local File Writing - Writes log entries to the device's local file system for later retrieval or upload.
- Performance Log Storage - Writes log entries to local storage on the device for later retrieval and analysis.
- Structured Log Ingestion - A local or remote server receives uploaded log files, parses them using the structured protocol, and saves the results.
- Log Aggregators - Combines logs from all sources into a single backend for unified analysis and problem discovery.
- Local Device - Writing log entries to device storage and viewing metadata of stored log files.
- Log Parsing - Parses uploaded logs using a structured protocol that extracts content, type, timestamp, thread name, thread ID, and main-thread flag.
- Binary Log Protocols - Defines a structured format for log entries that extracts content, type, timestamp, thread metadata, and main-thread flag.
- Structured Logging - Log entries are encoded with a defined binary protocol that includes content, type, timestamp, and thread metadata.
- Cross-Platform Logging Modules - The system provides a unified logging interface across iOS, Android, Web, and Flutter platforms.
- Log Browsers - A web-based interface allows searching, scanning, and inspecting parsed logs from multiple sessions.
- Cross-Platform Log Collectors - Collects, stores, and uploads client-side logs from iOS, Android, Web, and Flutter environments for centralized debugging.
- Client-Side Log Collectors - Captures and persists log entries on mobile and web devices for later retrieval and upload to a remote server.
- Log Search Engines - Provides a visual interface to search, scan, and browse uploaded logs from apps and web.
- Debug Log Uploaders - Transmits locally stored log files to a configured server endpoint for centralized collection and analysis.
- Client-Side Log Uploaders - Transmitting local log files to a remote server and receiving them for parsing and storage.
- Log Browsers - Provides a visual tool to search, scan, and inspect uploaded logs from apps and web browsers for debugging.
- Visual Log Browsers - Providing a visual interface to search, scan, and browse uploaded logs from apps and web.
- Log Receiving Servers - Starts a local server that receives uploaded log files, parses them, and saves the parsed output as text files.
- JavaScript 框架汇总 - Listed in the “JavaScript 项目” section of the Great Open Source Project awesome list.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
