Error Log Matching With LLMs for Faster Software Debugging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Debugging software with large and complex source code is time- and resource-consuming, especially for non-developer users, due to the complexity of parsing and understanding error logs, and identifying effective solutions for root causes.

Innovation Solution

A software debugging system that leverages large language models (LLMs) and entity matching models to generate embeddings for error logs, match historical errors, and propose solutions based on historical data, enabling efficient identification and mitigation of errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional manual debugging methods are used, then developers can identify and resolve errors, but the process becomes time- and resource-consuming especially for non-developer users

Engineering Contradiction:
Improvedebugging efficiencyVSAvoidtime required for error identification and resolution
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent introduces an intermediary system comprising error log analysis components, embedding generation models, and solution recommendation engines that mediate between the error logs and users. This intermediary automatically processes error logs, generates embeddings, identifies patterns, and recommends solutions, eliminating the need for users to manually parse complex error logs while maintaining high accuracy in error identification and resolution.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If complex error log parsing is performed manually, then accurate error identification is achieved, but the complexity burden falls heavily on non-expert users

Engineering Contradiction:
Improveerror identification accuracyVSAvoiduser effort required for debugging
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The system enables self-service debugging by automatically performing error log analysis, embedding generation, pattern recognition, and solution recommendation without requiring user expertise. The error processing component autonomously parses logs, the embedding model self-generates feature representations, and the solution recommendation engine automatically identifies and proposes fixes, allowing non-expert users to resolve errors with minimal effort while maintaining high accuracy.

Inventive Principle:
Principle #25Self-service

3Reliability

If comprehensive error log analysis is performed, then root causes are accurately identified, but the computational resources and time required increase significantly

Engineering Contradiction:
Improveroot cause identification accuracyVSAvoidcomputational resources for error analysis
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary actions by pre-processing error logs into standardized formats, pre-generating embeddings for common error patterns, and pre-building knowledge bases of known errors and solutions. When a new error occurs, the system compares it against pre-processed data and known patterns, significantly reducing the computational resources and time required for real-time analysis while maintaining high root cause identification accuracy.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12536089B2Application error log analysis and resolution using large language models and entity matching
Publication Date: 2026.01.27 SAP SE
  • US12536089B2 patent drawing
  • US12536089B2 patent drawing
  • US12536089B2 patent drawing

AI summary

Methods, systems, and computer-readable storage media for a software debugging system that leverages a LLM in combination with an entity matching model to propose solutions for mitigating errors. In some examples, the LLM is used to generate embeddings that are used to identify two or more matched historical errors. The matched historical errors are potential matches to a current error that needs to be resolved. The entity matching model is used to determine a matched historical error from the two or more matched historical errors. The LLM is also used to generate a proposed solution to the current error based on a historical solution to the matched historical error. The proposed solution can be executed to resolve the current error.