Application Log Management with Automatic Event-Based Uploads

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for managing application logs require user credentials, leading to user data privacy concerns and are time-consuming, with limited support for local failures and no immediate troubleshooting solutions.

Innovation Solution

A method and system that automatically generate and upload application log files, including API call URLs, responses, and payloads to an application server on predefined events, reducing server traffic and ensuring secure data handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If application log files are manually retrieved and analyzed, then troubleshooting can be performed, but user data privacy concerns arise and the process is time-consuming

Engineering Contradiction:

Improvetroubleshooting effectivenessVSAvoidtime to retrieve and analyze logs

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system automatically generates and uploads application log files to a server in advance, before any troubleshooting is needed. This preliminary action stores the logs securely on the server, eliminating the time-consuming manual retrieval process and preserving user data privacy since the logs are already uploaded without requiring user intervention.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If exact user data is collected to regenerate problem scenarios, then effective troubleshooting is possible, but user data privacy is compromised

Engineering Contradiction:

Improveproblem reproduction accuracyVSAvoiduser data privacy exposure

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system extracts only the necessary log data (API call URLs, responses, payloads, system information) required for troubleshooting and uploads it to the server. This extraction process captures sufficient information to reproduce and analyze problems without collecting or storing sensitive user personal data, thus maintaining privacy while enabling effective troubleshooting.

Inventive Principle:

Principle #2Taking out (Extraction)

3Ease of operation

If application log files are stored locally, then immediate access is possible, but memory consumption increases and data security is reduced

Engineering Contradiction:

Improvelog file accessibilityVSAvoidmemory consumption

Core Design Contradiction:

Ease of operationVSQuantity of substance

Solution Approach 1:

The system uses a server as an intermediary to store application log files. Instead of storing logs locally on user devices (which consumes memory), the logs are uploaded and stored on the server. Developers can access these logs through the server interface, maintaining ease of operation while significantly reducing local memory consumption and improving data security through centralized secure storage.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12379979B2Method and system for managing application logs

Publication Date: 2025.08.05 RAKUTEN SYMPHONY INC

AI summary

Embodiment herein provides a method for managing application logs by an system (100). The method includes detecting, by the system (100), event associated with application stored in the system (100) and creating, by the system (100), application log file while the event associated with the application is performed at the system (100). The application log file includes a URL used to call API associated with the application while the event is performed, a response received through the API associated with the application while the event is performed from an application server (1000) and a payload. The method also includes determining, by the system (100), that the event associated with the application is completed; and automatically uploading, by the system (100), the application log file and information associated with the system (100) to an application server (1000) corresponding to the application.