Patent Grant
8499240
Some embodiments relate to the reading and analysis of log files. More specifically, some embodiments relate to the rules-based presentation of log file messages on a graphical timeline.
The execution of computer programs and operation of computer hardware commonly result in the generation of error and informational messages regarding the programs or hardware. These messages are commonly stored in one or more “log files” associated with a system. A common task of administrators, support staff and users in general is the reading and analysis of these log files. Analysis is required to identify, diagnose and resolve system issues.
Log files are typically packed with data including messages and time stamps. Log files are difficult to read and generally are produced in a flat file which must be scanned to identify potential issues. The presentation of entries in such files makes it difficult for a human to interpret the density or currency of entries. This can make it difficult for a human to easily identify and troubleshoot problems.
It would be desirable to provide systems and methods for improving the presentation of log files so that errors, trends and issues can be more easily perceived and identified by humans.
Computer system 110 may include or be in communication with a number of processes, devices and systems that cause the creation of log files and log data. These log files and log data are used to track, diagnose or monitor the status of the processes, devices and systems. These log file messages may be obtained from a number of different log file message sources 116a-n as is known in the art. For example, in a typical network system, log file messages may be created for processes including, for example, an overall system configuration, a TCP/IP connection status, other network connection statuses, test routines, or the like. In many systems, designers or administrators create maintenance or diagnosis routines to monitor the status of different devices or systems. For example, a critical disk storage device may be monitored using a routine that generates log files. Data from any (or all) of such log file message sources 116a-n may be used pursuant to embodiments of the present invention.
Computer system 110 is in communication with one or more data storage devices such as filtering and aggregation rules data store 112 and log file data store 118. Filtering and aggregation rules data store 112 stores data, including one or more rules, for filtering and aggregating log file data so that it can be displayed on a graphical timeline. Data store 112 is accessible by UI service layer 114. In some embodiments, for example where log file data received from one or more log file message sources 116a-n is stored for future analysis, computer system 110 is further in communication with log file data store 118 for storing or archiving log file data. Pursuant to some embodiments, UI service layer 114 may cause the access of data from log file data store 118 to display log file data on a graphical timeline (e.g., so that the data is viewable by a user operating a user interface 120 in communication with the computer system 110).
Pursuant to some embodiments, computer system 110 receives data from one or more log file message sources 116a-n in the format generated by the log file message sources 116a-n. The data is then stored in log file data store 118. Log file data is retrieved for display on a user interface 120 using one or more filtering and aggregation rules stored in data store 112. Pursuant to some embodiments, the filtering and aggregation rules may be modified by a qualified user (e.g., such as a system administrator) so that log file messages may be combined, flagged, or otherwise presented in a manner which highlights important log file events for a user. For example, pursuant to some embodiments, messages may be filtered by their relative importance and aggregated with other events on a graphical timeline so that a user interacting with a user interface 120 may readily and quickly identify important events. In some embodiments, log file messages may be aggregated based on different logical components (or systems) so that related information is displayed in a coherent manner. Examples of some embodiments will be provided further below.
A user (e.g., such as an administrator or technician) may manipulate user interface 120 to interact with UI service layer 114 according to some embodiments. Such interactions may include requesting log file message reports, viewing current system status, monitoring system information, or the like. User interface 120 may be displayed by any suitable device. For example, the device may include any necessary software to support a proprietary interface (e.g., a proprietary client application) or execution engine (e.g., a Web browser). A device to display the user interfaces is capable of communication (including sporadic communication—e.g., mobile devices) with computer system 110.
As shown, user interface 200 includes an area 210 which displays a number of items of information in a graphical timeline. In the illustrative interface, the timeline is shown as extending horizontally, from left to right. Those skilled in the art will appreciate that other formats may also be used. In the illustrative interface, area 210 includes two primary portions, a set of data tracks 214a-n and a corresponding set of monitored components 216a-n. Each data track 214 provides a graphical illustration of the status of the corresponding monitored component 216. Pursuant to some embodiments, the data tracks 214 are color coded to reflect different statuses. For example, color codes may be selected to draw attention to those events or statuses which require attention (e.g., error or failure messages may be coded in red, satisfactory statuses may be coded in green, and warnings may be coded in yellow).
Each of the data tracks 214 are constructed using aggregated and filtered log file message data. For example, the data track 214d (associated with a monitored component 216d labeled as the “HTTP Proxy” component) may be constructed from a number of different log file messages received from a monitoring program associated with the HTTP Proxy component. For example, the monitoring program associated with the HTTP Proxy component may check the status of the HTTP Proxy component every minute (or some other frequency) and generate a log file message indicating the status of the HTTP Proxy component. Data track 214d may, thus, represent hundreds of individual log file messages associated with the HTTP Proxy component. As shown, for most of the displayed time period, the HTTP Proxy component was operating properly (or, put another way, the status of the HTTP Proxy component was in an acceptable state). However, at several points in time, the log file of the HTTP Proxy component included messages indicating the HTTP Proxy component was not in an acceptable state (shown in
Embodiments of the present invention allow these status changes (particularly status changes which indicate an unacceptable or undesirable status) to be quickly perceived by a human operator. Pursuant to some embodiments, an operator may move, position or hover a cursor or other pointer over the area to obtain more details (an example will be provided further below in conjunction with a discussion of
Each of the data tracks 214 may be constructed using log file data that is filtered and/or aggregated pursuant to one or more rules (e.g., from filtering and aggregation rules datastore 112 of
Embodiments of the present invention allow a variety of different filters and aggregations to occur. For example, filtering and aggregation rules may be created and stored in data store 112 of
Other data tracks 214 shown in
User interface 200 may include other tools to allow a user to easily navigate through log file data. For example, as shown, a user may select a date range using interface item 218. The interface item 218 is shown as a drop-down box in which the “last day” of log file graphical data is shown. Those skilled in the art will appreciate that users may be prompted to select time or date ranges in a number of ways so that a user may easily navigate data by time. For example, a user may select to view the last hour of activity, providing track data 214 having a greater degree of granularity. As another example, a user may select to see a week's worth of activity so that the user may readily identify potential error or other system or component trends. As shown, user interface 200 also includes one or more icons 220 allowing the user to scroll through data based on time or date. For example, as shown, where the user is viewing data from the last day of activity, scrolling to the left may reveal the previous day or hour's worth of log file activity. Again, this allows a user to quickly and readily assess trends and issues.
Reference is now made to
The screen portion 330 illustrates the data fields that may be provided by a message source (such as a message source 116 of
Visual cues and icons may also be presented in screen portion 330 to further assist users in quickly analyzing the presented data. For example, a triangle image may be added to a message when the message is associated with a status condition of “FAILURE”, while a square image may be added to messages that are associated with a status condition of “RESPONDING”. Other images or icons, including color coded images or icons, may be selected and appended to message data as desired.
The process 400 begins at 402 where a request to view log file data is received. The request at 402 may be received by system 110 of
As part of processing the request, any filter information associated with the request is identified (at 420). For example, the request may include information identifying a view or parameters associated with the particular log file data to be viewed. As a particular example, the request may include information identifying a time period over which to view the log file data (e.g., such as the last hour, the last 24 hours, the last week, etc.). At 420, this filter information or criteria are processed in order to retrieve the requested data. The requested information may be retrieved, for example, using code configured to extract the data from a data store such as data store 118 of
Processing continues at 430 where the log file data which matches the filter criteria is retrieved. As an example, if the filter criteria included a specification of a date range, the log file data matching the date range filter is retrieved at 430. As an example, the data may be retrieved using a database query to retrieve filtered data from a datastore such as the datastore 118 of
Processing continues at 440 where one or more aggregation rule(s) are determined. For example, pursuant to some embodiments, aggregation rules which define particular components or component groups may be applied to aggregate multiple log file messages for presentation. Referring to the illustrative user interface of
Processing continues at 450 where the filtered and aggregated data is displayed on a user interface, such as the user interface 120 of
In this manner, embodiments permit a user operating a user device to quickly and efficiently analyze and view log file data without the need to page through large amounts of difficult to read data records. Users, pursuant to some embodiments, may simply navigate through screens containing filtered and aggregated log file message data shown on a graphical timeline.
Each system described herein may be implemented by any number of devices in communication via any number of other public and/or private networks. Two or more of devices of may be located remote from one another and may communicate with one another via any known manner of network(s) and/or a dedicated connection. Moreover, each device may comprise any number of hardware and/or software elements suitable to provide the functions described herein as well as any other functions. Other topologies may be used in conjunction with other embodiments.
All systems and processes discussed herein may be embodied in program code stored on one or more computer-readable media. Such media may include, for example, a floppy disk, a CD-ROM, a DVD-ROM, a Zip™ disk, magnetic tape, and solid state RAM or ROM memories. Embodiments are therefore not limited to any specific combination of hardware and software.
The embodiments described herein are solely for the purpose of illustration. Those in the art will recognize other embodiments may be practiced with modifications and alterations limited only by the claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5847972 | Eick et al. | Dec 1998 | A |
| 5872909 | Wilner et al. | Feb 1999 | A |
| 6098101 | Sears | Aug 2000 | A |
| 6600501 | Israel et al. | Jul 2003 | B1 |
| 7099897 | Huras et al. | Aug 2006 | B2 |
| 7424718 | Dutton | Sep 2008 | B2 |
| 7509539 | Denefleh et al. | Mar 2009 | B1 |
| 7698686 | Carroll et al. | Apr 2010 | B2 |
| 7886202 | Lin et al. | Feb 2011 | B2 |
| 20060031719 | Bower et al. | Feb 2006 | A1 |
| 20070245238 | Fugitt et al. | Oct 2007 | A1 |
| 20090113246 | Sabato et al. | Apr 2009 | A1 |
| 20090199118 | Sabato et al. | Aug 2009 | A1 |
| Entry |
|---|
| Potter Scott, Event Driven Timeline Displays: Beyond Message Lists in Human-Intelligent System Interaction, 1991. |
| Number | Date | Country | |
|---|---|---|---|
| 20100115443 A1 | May 2010 | US |
