Microservice Log Tracing via Unified Call Relationship Display
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In microservice architecture, tracing the call relationship between multiple applications and analyzing log information to identify service issues is cumbersome and time-consuming due to unclear API call relationships, making it difficult to determine the stage at which a problem occurs during service provision.
Innovation Solution
A method involving log collecting agents in each application to issue and manage transaction IDs, enabling the tracing and display of log information across applications through API calls, allowing for the identification of problematic log information and its corresponding call relationship, thereby specifying the service stage where issues arise.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If log information of multiple applications is stored separately, then each application can maintain its own log data independently, but it becomes cumbersome and time-consuming to trace and analyze log information across applications to identify service issues
Solution Approach 1:
The patent merges log information from multiple separate applications into a unified log storage structure. The log collecting server aggregates logs from different applications and organizes them by call relationships, allowing analysts to trace service issues across application boundaries without manually accessing each application's separate log storage.
Solution Approach 2:
The patent introduces a log collecting server as an intermediary component between applications and log analysts. This mediator collects, standardizes, and organizes log information from multiple applications, then presents it in a unified format that reveals call relationships, eliminating the need for direct analysis of scattered log sources.
2Ease of operation
If log information from multiple applications is collected and displayed together, then it becomes easier to trace call relationships and identify service issues, but it increases the complexity of log management and data organization
Solution Approach 1:
The patent segments the log collection and management system into distinct functional components: log collecting agents deployed in individual applications, a central log collecting server for aggregation and processing, and a display unit for presentation. This segmentation allows each component to handle specific tasks independently, managing complexity through modular architecture while achieving unified log tracing capability.
Solution Approach 2:
The log collecting server acts as an intermediary that handles the complexity of data organization. It receives logs from multiple sources, processes them to establish call relationships, and presents organized information to users. This mediator absorbs the organizational complexity, leaving the user interface simple and easy to operate.
3Loss of information
If detailed log information from all applications is displayed, then complete information is available for analysis, but it becomes difficult to identify which log information corresponds to specific call relationships and service stages
Solution Approach 1:
The log collecting server serves as an intelligent intermediary that processes raw log information and adds contextual metadata indicating call relationships and service stages. It correlates logs from different applications based on service calls and presents them with annotations showing their relational context, making it easy to identify which log entries belong to which service stage without losing detailed information.
Solution Approach 2:
The patent adds a new dimension of organization to log information by incorporating call relationship metadata and service stage identifiers. Instead of displaying only chronological log entries, the system organizes logs in a multi-dimensional structure that includes service flow context, enabling users to trace call relationships across applications while maintaining access to complete detailed information.
Data Source
AI summary
The present disclosure relates to a method for tracing a call relationship in an MSA and displaying log information accordingly, and relates to a method of easily recognizing at which stage of service a problem has occurred when a problem occurs during a process of providing the entire service by multiple applications in microservice architecture.