Log System for Multi-Container Request Tracing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional log systems face difficulties in automatically extracting logs from multiple containers that collaboratively process requests, as redundant processing leads to logs being stored in databases, making it challenging to trace and extract error-related logs efficiently.
Innovation Solution
A log system that includes a storage device, circuitry for controlling application execution environments, and another circuitry for transmitting requests between these environments, allowing for the identification and storage of request information, process information, and logs in a structured manner, enabling the log extractor to trace the flow of requests and extract relevant logs automatically.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If logs are stored in databases for each container, then log data can be preserved, but it becomes difficult to automatically extract and trace error-related logs across multiple containers
Solution Approach 1:
The patent introduces a log management server as an intermediary component that centralizes log collection from multiple containers. This server receives logs from each container, stores them in a unified database, and provides automated extraction capabilities through request flow tracing, thereby resolving the contradiction between preserving log data and enabling efficient extraction.
Solution Approach 2:
The patent merges分散 logs from multiple containers into a single centralized log database managed by the log management server. This consolidation allows logs that were previously scattered across individual container databases to be unified and easily traceable through automated request flow analysis, improving both preservation and extraction efficiency.
2Adaptability or versatility
If multiple containers collaboratively process requests, then system functionality is enhanced, but tracing the flow of requests and extracting relevant logs becomes complex
Solution Approach 1:
The patent implements a feedback mechanism where the log management server automatically traces request flows by analyzing log data from multiple containers. The server correlates request IDs across different containers to reconstruct the complete request flow, providing automated feedback about which logs are relevant to specific requests, thereby reducing tracing complexity while maintaining system versatility.
Solution Approach 2:
The patent applies preliminary action by having each container include request identification information in its logs before processing completes. This pre-structuring of log data with request IDs enables the log management server to efficiently trace request flows without complex real-time analysis, simplifying the extraction process while supporting multi-container functionality.
3Measurement precision
If request information is added to track flow across containers, then log extraction accuracy is improved, but data transmission volume increases
Solution Approach 1:
The patent extracts only the essential request identification information (request IDs) from the complete request data and includes it in log transmissions. This selective extraction provides sufficient precision for tracing request flows across containers without transmitting the entire request payload, thereby maintaining extraction accuracy while minimizing data transmission volume.
Data Source
AI summary
A log system includes, a storage device, first circuitry configured to control the application execution environments, and second circuitry configured to transmit each of the requests to a selected one of the application execution environments, wherein a first application execution environment is configured to, execute a first process for processing the first request, add second request information to the second request, transmit the added second request to the second circuitry, execute first output of process information identifying a first process, reception information identifying the first application execution environment, the second request information, source information identifying the first application execution environment, and a first log, wherein the second circuitry is configured to, transmit the second request to a second application execution environment, and execute second output of the source information identifying the first application execution environment, destination information identifying the second application execution environment, and the second request information.