IP Library Granted Patent US 12,379,979
Granted Patent B2
US 12,379,979 · App. 17/923,460 · Granted Aug 5, 2025

Method and system for managing application logs

Inventors: Arshil Shaikh (Indore, IN); Rounak Lahoti (Indore, IN); Shekh Shadab (Indore, IN); Himani Neema (Indore, IN)
Assignee: RAKUTEN SYMPHONY, INC.
G06F9/542G06F9/541
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,379,979
App. No.
17/923,460
Granted
Aug 5, 2025
Kind
B2
Abstract

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.

Claims (53)

1. A method for managing application logs by a system ( 100 ), wherein the method comprises:

detecting, by the processor ( 180 ) of the system ( 100 ), at least one event associated with at least one application stored in the system ( 100 );

creating, by the processor ( 180 ), at least one application log file while the at least one event associated with the at least one application is performed at the system ( 100 ), wherein the at least one application log file comprises a uniform resource locator (URL) used to call at least one application program interface (API) associated with the at least one application while the at least one event is performed, a response received through the at least one API associated with the at least one application while the at least one event is performed from an application server ( 1000 ) and a payload associated with the at least one event;

determining, by the processor ( 180 ), that the at least one event associated with the at least one application is completed; and

automatically uploading, by the processor ( 180 ), the at least one application log file and at least one information associated with the system ( 100 ) to the application server ( 1000 ) corresponding to the at least one application.

2. The method as claimed in claim 1 , wherein creating, by the processor ( 180 ), the at least one application log file while the at least one event associated with the at least one application is performed at the system ( 100 ) comprises:

determining, by the processor ( 180 ), data entered by a user to the processor ( 180 ), the URL used to call the at least one API associated with the at least one application while the at least one event is performed; the response received from the application server ( 1000 ), through the at least one API associated with the at least one application while the at least one event is performed and the payload associated with the at least one event while the at least one event associated with the at least one application is performed at the system ( 100 );

continuously writing, by the processor ( 180 ), the data entered by the user to the system ( 100 ), the URL used to call the at least one API associated with the at least one application while the at least one event is performed; the response received from the application server ( 1000 ), through the at least one API associated with the at least one application while the at least one event is performed and the payload associated with the at least one event while the at least one event associated with the at least one application is performed at the system ( 100 ) to the at least one application log file; and

creating, by the processor ( 180 ), the at least one application log file while the at least one event associated with the at least one application is performed at the system ( 100 ).

3. The method as claimed in claim 2 , wherein creating, by the processor ( 180 ), the at least one application log file while the at least one event associated with the at least one application is performed at the system ( 100 ) comprises:

determining, by the processor ( 180 ), an event status associated with the at least one event as one of a failed event and a successful event;

appending, by the processor ( 180 ), at least one of: an event status parameter and a color strip indicating the event status associated with the at least one event, to the at least one application log file; and

creating, by the processor ( 180 ), the at least one application log file.

4. The method as claimed in claim 1 , further comprising:

determining, by the processor ( 180 ), whether the upload of the at least one application log file and the at least one information associated with the system ( 100 ) to the application server ( 1000 ) corresponding to the at least one application is successful; and

performing, by the processor ( 180 ), one of:

determining a location of the at least one application log file stored in a memory ( 120 ) of the system ( 100 ) and deleting the at least one application log file stored in the memory ( 120 ) of the system ( 100 ), in response to determining that the upload of the at least one application log file and the at least one information associated with the system ( 100 ) to the application server ( 1000 ) corresponding to the at least one application is successful, and

detecting a user login to the application, determining the at least one application log file in the memory ( 120 ) of the system ( 100 ), uploading the at least one application log file stored in the memory ( 120 ) of the system ( 100 ) to the application server ( 1000 ), and deleting the at least one application log file stored in the memory ( 120 ) of the system ( 100 ), in response to determining that the upload of the at least one application log file and the at least one information associated with the system ( 100 ) to the application server ( 1000 ) corresponding to the at least one application is not successful.

5. The method as claimed in claim 1 , wherein the at least one information associated with the system ( 100 ) comprises at least one of: username associated with the application in the system ( 100 ), an application version running on the system ( 100 ), a date of the at least one event detected on the system ( 100 ), data inserted by a user to the application in the system ( 100 ).

6. The method as claimed in claim 1 , further comprising:

receiving, by the application server ( 1000 ), the at least one information associated with the system ( 100 ) as an input;

filtering, by the application server ( 1000 ), the at least one application log file of a plurality of application log files corresponding to the received at least one information associated with the system ( 100 );

receiving, by the application server ( 1000 ), a request to download the filtered at least one application log file of the plurality of application log files corresponding to the received at least one information associated with the system ( 100 );

downloading, by the application server ( 1000 ), the at least one application log file of the plurality of application log files corresponding to the received at least one information associated with the system ( 100 ); and

regenerating, by the application server ( 1000 ), the at least one event detected in the system ( 100 ) based on the at least one application log file.

7. The method as claimed in claim 1 , wherein automatically uploading, by the processor ( 180 ), the application log file and the at least one information associated with the system ( 100 ) comprises:

checking, by the processor ( 180 ), the at least one application log file is available in the memory ( 120 ) of the system ( 100 ) at an elapse of a time threshold; and

automatically uploading, by the processor ( 180 ), the at least one application log file available in the memory ( 120 ) of the system ( 100 ) and the at least one information associated with the system ( 100 ) to the application server ( 1000 ).

8. A system ( 100 ) for managing application logs, wherein the system ( 100 ) comprises:

a memory ( 120 );

a processor ( 180 ) coupled to the memory ( 120 );

a communicator ( 160 ) coupled to the memory ( 120 ) and the processor ( 180 ) and wherein the processor ( 180 ) is configured to:

detect at least one event associated with at least one application stored in the system ( 100 );

create at least one application log file while the at least one event associated with the at least one application is performed at the system ( 100 ), wherein the at least one application log file comprises a URL used to call at least one API associated with the at least one application while the at least one event is performed, a response received through the at least one API associated with the at least one application while the at least one event is performed from an application server ( 1000 ) and a payload associated with the at least one event;

determine that the at least one event associated with the at least one application is completed; and

automatically upload the at least one application log file and at least one information associated with the system ( 100 ) to the application server ( 1000 ) corresponding to the at least one application.

9. The system ( 100 ) as claimed in claim 8 , wherein the processor ( 180 ) is configured to create the at least one application log file while the at least one event associated with the at least one application is performed at the system ( 100 ) comprises:

determine data entered by a user to the system ( 100 ), the URL used to call the at least one API associated with the at least one application while the at least one event is performed; the response received from the application server ( 1000 ), through the at least one API associated with the at least one application while the at least one event is performed and the payload associated with the at least one event while the at least one event associated with the at least one application is performed at the system ( 100 );

continuously write the data entered by the user to the system ( 100 ), the URL used to call the at least one API associated with the at least one application while the at least one event is performed; the response received from the application server ( 1000 ), through the at least one API associated with the at least one application while the at least one event is performed and the payload associated with the at least one event while the at least one event associated with the at least one application is performed at the system ( 100 ) to the at least one application log file; and

create the at least one application log file while the at least one event associated with the at least one application is performed at the system ( 100 ).

10. The system ( 100 ) as claimed in claim 9 , wherein the processor ( 180 ) is configured to create the at least one application log file while the at least one event associated with the at least one application is performed at the system ( 100 ) comprises:

determine an event status associated with the at least one event as one of a failed event and a successful event;

append at least one of: an event status parameter and a color strip indicating the event status associated with the at least one event, to the at least one application log file; and

create the at least one application log file.

11. The system ( 100 ) as claimed in claim 8 , wherein the processor ( 180 ) is further configured to:

determine whether the upload of the at least one application log file and the at least one information associated with the system ( 100 ) to the application server ( 1000 ) corresponding to the at least one application is successful; and

perform one of:

determine a location of the at least one application log file stored in a memory ( 120 ) of the system ( 100 ) and delete the at least one application log file stored in the memory ( 120 ) of the system ( 100 ), in response to determining that the upload of the at least one application log file and the at least one information associated with the system ( 100 ) to the application server ( 1000 ) corresponding to the at least one application is successful, and

detect a user login to the application, determine the at least one application log file in the memory ( 120 ) of the system ( 100 ), upload the at least one application log file stored in the memory ( 120 ) of the system ( 100 ) to the application server ( 1000 ), and delete the at least one application log file stored in the memory ( 120 ) of the system ( 100 ), in response to determining that the upload of the at least one application log file and the at least one information associated with the system ( 100 ) to the application server ( 1000 ) corresponding to the at least one application is not successful.

12. The system ( 100 ) as claimed in claim 8 , wherein the at least one information associated with the system ( 100 ) comprises at least one of: username associated with the application in the system ( 100 ), an application version running on the system ( 100 ), a date of the at least one event detected on the system ( 100 ), data inserted by a user to the application in the system ( 100 ).

13. The system ( 100 ) as claimed in claim 8 , wherein the processor ( 180 ) is configured to automatically upload the application log file and the at least one information associated with the system ( 100 ) comprises:

check the at least one application log file is available in the memory ( 120 ) of the system ( 100 ) at an elapse of a time threshold; and

automatically upload the at least one application log file available in the memory ( 120 ) of the system ( 100 ) and the at least one information associated with the system ( 100 ) to the application server ( 1000 ).

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 22, 2024
From: RAKUTEN SYMPHONY SINGAPORE PTE LTD
To: RAKUTEN SYMPHONY, INC.
Reel/Frame 068466/0598 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 7, 2022
From: SHAIKH, ARSHIL; LAHOTI, ROUNAK; SHADAB, SHEKH; NEEMA, HIMANI
To: RAKUTEN SYMPHONY SINGAPORE PTE. LTD.
Reel/Frame 061676/0553 →
Priority Claims (1)
IN 202241039118 · Jul 7, 2022 · national
Continuity (1)
Related Publication 20250077314A1 · Mar 6, 2025
References Cited (10)
US 20070207800A1 · Daley et al. · 2007 [cited by applicant]
US 20140109188A1 · Pavlov · 2014 [cited by examiner]
US 20160019102A1 · Cui · 2016 [cited by examiner]
US 20190026163A1 · Subbiah et al. · 2019 [cited by applicant]
US 20190163610A1 · Vent · 2019 [cited by applicant]
US 20200081814A1 · Srinivasan · 2020 [cited by examiner]
US 20210357397A1 · Jha et al. · 2021 [cited by applicant]
Written Opinon dated Jan. 10, 2023 in International Application No. PCT/US22/43270. [cited by applicant]
International Search Report dated Jan. 10, 2023 in International Application No. PCT/US22/43270. [cited by applicant]
Åström, “Log File Highlighter”, Visual Studio, 2022, pp. 1-5 (5 Pages total). [cited by applicant]