System and method enabling multiple processes to efficiently log events
First Claim
1. A system for logging an event, comprising:
- a computer system including a CPU and memory;
a server-side logging component comprised in the memory of the computer system;
a means for persistently storing information;
a first client-side logging component comprised in the memory of the computer system;
a first executable module, wherein the first executable module is executable to call the first client-side logging component in order to log an event, wherein the event comprises an event level;
wherein the first executable module calling the first client-side logging component comprises the first executable module passing information specifying the event level to the first client-side logging component, wherein the first client-side logging component calling the server-side logging component comprises the first client-side logging component passing information specifying the event level to the server-side logging component;
wherein the server-side logging component persistently logging the event comprises the server-side logging component persistently logging the event level;
wherein, in response to said first executable module calling the first client-side logging component in order to log an event, the first client-side logging component is executable to call the server-side logging component in order to log the event;
wherein, in response to said first client-side logging component calling the server side logging component in order to log the event, the server-side logging component is executable to utilize the means for persistently storing information in order to persistently log the event.
0 Assignments
0 Petitions
Accused Products
Abstract
A system and method for enabling multiple processes to efficiently log events is described. A client executable module that needs to log an event may interface with a module or component referred to as a “client-side logging component”, passing various types of information regarding the event, such as an associated event level, one or more event associated event categories, an informational message, etc. The client-side logging component may maintain event logging criteria specifying which types of events should be logged. If the event should be logged, the client-side logging component may queue the event information and return execution control the client module. The event information may then be asynchronously retrieved from the event queue and sent to a server-side logging component. The server-side logging component may persistently log the event information in any of various ways, e.g., by storing it in a file, a database, etc. Processes running on multiple computers may call the server-side logging component to log events, via a client-side logging component instance associated with the process. A logging administration tool may be utilized in order to set event logging criteria. In response to being configured with new event logging criteria information, the server-side logging component may automatically propagate the logging criteria information to each of the client-side logging components. The client-side logging components may then being using the new logging criteria, dynamically changing the filtering of events that are sent to the server-side logging component.
-
Citations
41 Claims
-
1. A system for logging an event, comprising:
-
a computer system including a CPU and memory;
a server-side logging component comprised in the memory of the computer system;
a means for persistently storing information;
a first client-side logging component comprised in the memory of the computer system;
a first executable module, wherein the first executable module is executable to call the first client-side logging component in order to log an event, wherein the event comprises an event level;
wherein the first executable module calling the first client-side logging component comprises the first executable module passing information specifying the event level to the first client-side logging component, wherein the first client-side logging component calling the server-side logging component comprises the first client-side logging component passing information specifying the event level to the server-side logging component;
wherein the server-side logging component persistently logging the event comprises the server-side logging component persistently logging the event level;
wherein, in response to said first executable module calling the first client-side logging component in order to log an event, the first client-side logging component is executable to call the server-side logging component in order to log the event;
wherein, in response to said first client-side logging component calling the server side logging component in order to log the event, the server-side logging component is executable to utilize the means for persistently storing information in order to persistently log the event. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 12, 13, 14, 15, 16, 17, 18)
-
-
10. A system for logging an event, comprising:
-
a computer system including a CPU and memory;
a server-side logging component comprised in the memory of the computer system;
a means for persistently storing information;
a first client-side logging component comprised in the memory of the computer system;
a first executable module, wherein the first executable module is executable to call the first client-side logging component in order to log an event;
wherein, in response to said first executable module calling the first client-side logging component in order to log an event, the first client-side logging component is executable to store the event in a queue and return execution control to the first executable module prior to evaluating the event;
wherein said first client-side logging component calling the server-side logging component comprises the first client-side logging component asynchronously retrieving the event from the queue and then calling the server-side logging components wherein, in response to said first executable module calling the first client-side logging component in order to log an event, the first client-side logging component is executable to call the server-side logging component in order to log the event;
wherein, in response to said first client-side logging component calling the server-side logging component in order to log the event, the server-side logging component is executable to utilize the means for persistently storing information in order to persistently log the event. - View Dependent Claims (11)
-
-
19. A system for logging an event, comprising:
-
a first computer system including a CPU and memory;
a second computer system including a CPU and memory;
a server-side logging component comprised in the memory of the first computer system;
a means for persistently storing information;
a first client-side logging component comprised in the memory of the second computer system;
a first executable module running on the second computer system, wherein the first executable module is executable to call the first client-side logging component in order to log a first event;
wherein, in response to said first executable module calling the first client-side logging component in order to log a first event, the first client-side logging component is executable to call the server-side logging component in order to log the first event;
wherein, in response to said first client-side logging component calling the server-side logging component in order to log the first event, the server-side logging component is executable to utilize the means for persistently storing information in order to persistently log the first event. - View Dependent Claims (20, 21)
-
-
22. A method for logging an event, comprising:
-
a first executable module calling a first client-side logging component in order to log an event, wherein the first executable module and the first client-side logging component are stored in the memory of a computer system and execute on the computer system;
the first client-side logging component calling a server-side logging component in order to log the event, in response to said first executable module calling the first client-side logging component, wherein the server-side logging component is stored in the memory of the computer system and executes on the computer system;
wherein the event comprises an event level;
wherein said first executable module calling the first client-side logging component comprises the first executable module passing information specifying the event level to the first client-side logging component;
wherein said first client-side logging component calling the server-side logging component comprises the first client-side logging component passing information specifying the event level to the server-side logging component;
the server-side logging component persistently storing information in order to persistently log the event, in response to said first client-side logging component calling the server-side logging component;
wherein said server-side logging component persistently logging the event comprises the server-side logging component persistently logging the event level. - View Dependent Claims (23, 24, 25, 26, 27, 28, 29, 30, 33, 34, 35, 36, 37, 38)
-
-
31. A method for logging an event, comprising:
-
a first executable module calling a first client-side logging component in order to log an event, wherein the first executable module and the first client-side logging component are stored in the memory of a computer system and execute on the computer system;
the first client-side logging component calling a server-side logging component in order to log the event, in response to said first executable module calling the first client-side logging component, wherein the server-side logging component is stored in the memory of the computer system and executes on the computer system;
wherein, in response to said first executable module calling the first client-side logging component in order to log an event, the first client side logging component stores the event in a queue and return execution control to the first executable module prior to evaluating the event;
wherein said first client-side logging component calling the server-side logging component comprises the first client-side logging component asynchronously retrieving the event from the queue and then calling the server-side logging component;
the server-side logging component persistently storing information in order to persistently log the event, in response to said first client-side logging component calling the server-side logging component. - View Dependent Claims (32)
-
-
39. A method for logging an event, comprising:
-
a first executable module calling a first client-side logging component in order to log a first event, wherein the first executable module and the first client-side logging component are stored in the memory of a first computer system and execute on the first computer system, the first client-side logging component calling a server-side logging component in order to log the first event, in response to said first executable module calling the first client-side logging component, wherein the server-side logging component is stored in the memory of a second computer system and executes on the second computer system;
the server-side logging component persistently storing information in order to persistently log the first event, in response to said first client-side logging component calling the server-side logging component. - View Dependent Claims (40, 41)
-
Specification