Log management system and method

• US 7,707,189 B2
• Filed: 10/05/2004
• Issued: 04/27/2010
• Est. Priority Date: 10/05/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Haselden, J. Kirk, Ivanov, Sergei
• Primary Examiner(s): Ly; Cheyne D
• Application Number:
  US10/958,848
• Publication Number:
  US 20060075308A1
• Time in Patent Office: 2,030 Days
• Field of Search: 707/10, 707/204, 707/3, 707/5, 707/6, 707/104.1
• US Class Current: 707/672
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: H04L 41/0604 using filtering, e.g. reduction of information by using priority, element types, position or time

Abstract

A system and method for managing log entries associated with execution events in an application. The system and method may include a log provider wrapper for receiving log entries associated with the event and log providers for receiving all or part of the information associated with a log entry. The log provider wrapper, through communication with a logging configuration, may filter the log entry, segment information contained in the log entry, format the information, and deliver the information to one or more log providers. The log providers may send the information to a respective destination medium.

Claims

1. A system comprising a processor for managing event logging, comprising:

a log provider wrapper for determining whether log entry data associated with an event should be generated and, if the log entry data should be generated, for receiving the log entry data;

a plurality of log providers for writing log entries to one or more destinations, wherein the log provider wrapper filters information contained in the log entry data, segments the information contained in the log entry data such that a first segment contains a first part of the information and a second segment contains a second part of the information, selects one or more of said log providers, and sends the segmented information contained in the log entry data to one or more selected log providers, wherein the log provider wrapper and plurality of log providers permit contingent generation of log entry data and permit different log entries to be written to a plurality of destinations based on the generated log entry data; and

a logging configuration in communication with the log provider wrapper, comprising at least one of a filtering rule, a destination for a log entry, or a format for a log entry, wherein the log provider wrapper selects the log providers based on the logging configuration.

2. The system of claim 1, wherein the system for managing event logging is based on an object model.

3. The system of claim 2, wherein the event is an event object, and the logging configuration is a parent object of the event object.

4. The system of claim 1, wherein a log provider filters the information contained in the log entry data.

5. The system of claim 4, wherein the log provider filtering the information results in logging a portion of the information.

6. The system of claim 1, wherein the log providers format the information contained in the log entry data for compatibility with a destination to which the information will be sent.

7. The system of claim 1, wherein a log provider sends segmented information as a log entry to a destination.

8. The system of claim 1, wherein the log provider wrapper sends the first segment of the information to a first log provider and the second segment of the information to a second log provider.

9. The system of claim 1, wherein an added log provider is added to the plurality of log providers of the system for managing event logging.

10. The system of claim 9, wherein the log provider wrapper filters the information contained in the log entry data, selects the added log provider, and sends the information contained in the log entry data to the added log provider.

11. A processor-implemented method for managing event logging in an application, comprising:

determining, via the processor, whether log entry data comprising information related to an event should be generated, thereby permitting contingent generation of log entry data;

if the log entry data should be generated, receiving the log entry data; and

determining, via the processor, in accordance with a logging configuration comprising at least one of a filtering rule, a destination for a log entry, or a format for a log entry, what part of the log entry data should be recorded by;

segmenting the information contained in the log entry data into a plurality of segments, wherein each segment comprises a respective portion of the information contained in the log entry data;

filtering the information contained in the log entry data by determining if one or more log providers in a system are interested in any of the plurality of segments of the information contained in the log entry data; and

sending a segment of the information contained in the log entry data to a log provider interested in the segment, thereby permitting different log entry data to be sent to a plurality of log providers based on the generated log entry data.

12. The method of claim 11, further comprising:

sending the segment of the information contained in the log entry data to a destination.

13. The method of claim 12, further comprising:

filtering the segment of the information contained in the log entry data prior to sending the segmented information to the destination, wherein the filtering is completed by the log provider.

14. The method of claim 11, further comprising:

notifying a log provider wrapper of a potential log entry;

determining interest in the log entry data; and

communicating the interest in the log entry data to the event.

15. The method of claim 11, further comprising:

formatting the information in the log entry data so that it is compatible with at least one of the log provider and the destination.

16. The method of claim 11, further comprising:

initializing the event;

displaying a potential log entry to a user; and

receiving a selection of the log entry.

17. A computer-readable storage medium having computer-executable instructions for performing steps, comprising:

determining whether log entry data comprising information related to an event should be generated, thereby permitting contingent generation of log entry data;

if the log entry data should be generated, receiving the log entry data determining, in accordance with a logging configuration comprising at least one of a filtering rule, a destination for a log entry, or a format for a log entry, what part of the log entry data should be recorded by;

segmenting the information contained in the log entry data into a plurality of segments, wherein each segment comprises a respective portion of the information contained in the log entry data;

filtering the information contained in the log entry data by determining if one or more log providers in a system are interested in any of the plurality of segments of the information contained in the log entry data; and

sending a segment of the information contained in the log entry data to a log provider interested in the segment, thereby permitting different log entry data to be sent to a plurality of log providers based on the same log entry data.

18. The computer-readable storage medium of claim 17, having further computer-executable instructions for performing the steps of:

notifying a log provider wrapper of a potential log entry;

determining interest in the log entry data; and

communicating the interest in the log entry data to the event.

19. The computer-readable storage medium of claim 17, having further computer-executable instructions for performing the steps of:

displaying a potential log entry to a user;

receiving a selection of the log entry; and

adding a log provider based on the selection.

20. A processor-implemented method for managing event logging in an application, comprising:

notifying a log provider wrapper of a potential log entry;

determining, via the processor, interest in the potential log entry;

if there is interest in the potential log entry, receiving the potential log entry comprising information related to an event, comprising at least one of a filtering rule, a destination for a log entry, or a format for a log entry, thereby permitting contingent receipt of potential log entry information;

segmenting the information contained in the potential log entry into a plurality of segments, the plurality of segments including a first segment and a second segment, wherein the first segment includes a first portion of the information and the second segment includes a second portion of the information;

filtering the information contained in the potential log entry by determining if one or more of a plurality of log providers in a system are interested in any of the plurality of segments of the information contained in the log entry;

formatting the potential log entry information so that it is compatible with at least one of the log provider and the destination; and

sending the first segment to a log provider interested in the first segment and the second segment to a log provider interested in the second segment, thereby permitting different potential log entry information to be sent to the plurality of log providers based on the information related to the event.