Distributed Service Log Correlation With Unique Service Codes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software log processing methods struggle with inefficiencies in complex service scenarios, leading to storage pressure, irreproducibility, difficulty in locating issues, and inconsistent log norms, which affect debugging efficiency and system robustness.

Innovation Solution

A software log processing method that records logs based on unique service codes, concatenates log contents, and classifies them by service process, enabling quick problem identification and reducing storage volume by selective recording.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If all logs are recorded in formal environment, then complete log information is obtained, but storage pressure increases significantly

Engineering Contradiction:
Improvelog information completenessVSAvoidstorage volume
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent segments log recording by service process, dividing logs into different groups corresponding to different service stages. This allows selective recording of logs based on service type and importance, rather than recording all logs uniformly, thus reducing storage pressure while maintaining necessary log completeness for debugging.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by applying different log recording strategies to different service processes. Critical service processes record detailed logs, while less critical processes record summarized or selective logs. This differentiated approach optimizes storage usage based on the specific needs of each service area.

Inventive Principle:
Principle #3Local quality

2Quantity of substance

If logs are recorded by level (e.g., error logs only), then storage pressure is reduced, but detailed log information is lost making problem screening difficult

Engineering Contradiction:
Improvestorage volumeVSAvoidproblem detection difficulty
Core Design Contradiction:
Quantity of substanceVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements dynamic log recording where the log level and detail are adjusted based on the service process stage and detected anomalies. During normal operation, summarized logs are recorded to reduce storage. When errors or anomalies are detected, the system dynamically switches to recording detailed logs at higher levels, ensuring problem detection capability is maintained when needed.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent performs preliminary classification of service processes and pre-determines log recording strategies for each service type. This preliminary action allows the system to automatically apply appropriate logging levels without manual intervention, balancing storage efficiency with problem detection capability based on pre-analyzed service characteristics.

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If logs are recorded without unique service code tracking, then log recording is simple, but logs cannot be traced through service processes making problem location time-consuming

Engineering Contradiction:
Improvelog recording complexityVSAvoidproblem location time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent introduces unique service codes as intermediaries that link different log entries across service processes. Each service process is assigned a unique code that is embedded in all related logs, acting as a mediator that allows rapid tracing and correlation of logs through the entire service lifecycle without complex manual tracking mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The unique service code serves multiple functions simultaneously: it identifies the service process, traces log relationships, enables rapid problem location, and supports log aggregation. This multi-functional approach reduces the need for separate tracking mechanisms while improving problem location efficiency.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If development team uses non-uniform log norms, then coding flexibility is maintained, but log consistency deteriorates making maintenance difficult

Engineering Contradiction:
Improvecoding flexibilityVSAvoidlog consistency
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent changes the parameter of log recording from developer-discretionary to system-mandated by introducing standardized service code parameters. The system automatically assigns and enforces unique service codes and standardized log formats, transforming log recording from a flexible but inconsistent practice to a consistent, parameter-driven process that maintains both flexibility and stability.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent implements feedback mechanisms where the log system automatically validates and corrects log entries to ensure consistency with established norms. When logs deviate from standardized formats, the system provides feedback and enforcement, ensuring long-term consistency while allowing developers flexibility in service implementation details.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4471602B1Software log processing method
Publication Date: 2025.10.22 SHENZHEN ANKE BAITENG TECH CO LTD
  • EP4471602B1 patent drawingFigure 1
  • EP4471602B1 patent drawingFigure 2
  • EP4471602B1 patent drawingFigure 3

AI summary

The present invention relates to the technical field of processing software logs, in particular a software log processing method, the present invention has the advantages of following up the unique service code enables all log contents to be automatically concatenated into a log block, and the system to concurrently count execution time, warnings and errors generated in each process, enabling the O&M operators and developers to quickly locate the problems when dealing with them at a later stage, in the scenarios such as a distributed system and microservice system, making it possible to unify the logs scattered in each system to the log platform for storage by way of the unique service code, as well as concatenate the execution timing in each system, greatly raising the treatment efficiency for the problems in the microservices or the distributed system and improving the maintainability of the distributed system or the microservice system.