INTERFACE FOR MANAGING SPLITTABLE TIMESTAMPS ACROSS EVENT RECORDS

Embodiments are directed towards a graphical user interface to identify locations within event records with splittable timestamp information. A display of event records is provided using any of a variety of formats. A splittable timestamp selector allows a user to select one or more locations within event records as having time related information that may be split across the one or more locations, including, information based on date, time of day, day of the week, or other time information. Any of a plurality of mechanisms is used to associate the selected locations with the split timestamp information, including tags, labels, or header information within the event records. In other embodiments, a separate table, list, index, or the like may be generated that associates the selected locations with the split timestamp information. The split timestamp information may be used within extraction rules for selecting subsets of the event records.

DETAILED DESCRIPTION

In addition, as used herein, the term “or” is an inclusive “or” operator, and is equivalent to the term “and/or,” unless the context clearly dictates otherwise. The term “based on” is not exclusive and allows for being based on additional factors not described, unless the context clearly dictates otherwise. In addition, throughout the specification, the meaning of “a,” “an,” and “the” include plural references. The meaning of “in” includes “in” and “on.” For example embodiments, the following terms are also used herein according to the corresponding meaning, unless the context clearly dictates otherwise.

The term “machine data” as used herein may include data generated by machines, including, but not limited to, server logs or other types of event data, including event records. In at least one of various embodiments, machine data streams may be time stamped to create time stamped events. For example, information processing environments, such as, firewalls, routers, web servers, application servers and databases may generate streams of time series data in the form of events. In some cases, events may be generated hundreds or thousands of times per second. In some embodiments, the machine data may be unstructured data, structured data, and/or a combination thereof: Unstructured data may refer to data that does not include at least one predefined field.

The term “extraction rule” and/or “data field extraction rule” may refer to instructions that may be applied to identify and extract field values from data, such as event records. In some embodiments, extraction rule may define a field within event records from which to extract a value. In at least one of various embodiments, the extraction rules may include regular expressions. The data from which extraction rules may be applied may include structured and/or unstructured machine data, indexed, non-indexed, event records, or other type of data.

The term “regular expression” as used herein refers to a sequence of constants and operators arranged into expressions for matching a set of strings. A regular expression is often defined as a pattern matching language which can be employed to identify character strings, for example, to select specific strings from a set of character strings. More particularly, regular expressions are often defined as a context-independent syntax that can represent a wide variety of character sets and character set orderings. In operation, regular expressions can be employed to search data based upon a predefined pattern or set of patterns. As such, this pattern matching language employs a specific syntax by which particular characters or strings are selected from a body of text. Although simple examples of regular expressions can be easily understood, oftentimes, the syntax of regular expressions are so complex that even the most experienced programmers have difficulty in understanding them. Regular expressions may be constructed using a variety of computer languages and constructs. In addition to matching, some regular expression systems offer functionality, such as, substitution, grouping, back references, or the like. Regular expressions and regular expression systems may be adapted to work with non-string data providing matching facilities for binary data.

The term “event record” may refer to computing data that is collected about an event for a computing system, including, for example, an action, characteristic, condition (or state) of the computing system. For example, such events may be about a computing system's performance, actions taken by the computing system, or the like. Event records may be obtained from various computing log files generated by the computer's operating system, and/or other monitoring application. However, event records are not restricted by a file format or structure from which the event data is obtained. In various embodiments, event records may include structured and/or unstructured machine data.

The phrase “location within an event record” refers to one or more sequential characters (e.g., a string) within the event record. The location with the event record, in some embodiments, may be definable based on various delimiters used to separate portions of the event record. However, the location within the event record may also be definable based on a characteristic of the data within the event record that might be used in an extraction rule; based on a starting column or position within the event record; or any of a variety of other criteria.

Briefly stated, various embodiments are directed towards providing a graphical user interface usable to identify one or more locations within event records with splittable timestamp information. A display of a plurality of event records is provided to a user through a display interface device using any of a variety of formats. A splittable timestamp selector is displayed that allows the user to select one or more locations within event records as having time information that may be split across the one or more locations. For example, the user might select one location within the event records as having date information, another location as having time of day information, and yet another location as having day of the week information, or so forth. The subject innovations are not limited however to these non-limiting, non-exhaustive examples for splitting timestamp information across locations within the event records, and other arrangements and/or allocations are also allowed. Therefore, in some embodiments, the user might uniquely identify a decomposition or splitting for the timestamps. Any of a plurality of mechanisms may then be used to associate the selected locations with the split timestamp information, including, but not limited to tags, labels, or additional field header information within the event records. In other embodiments, a separate table, list, index, or the like, may be generated that associates the locations within the event records with the split timestamp information. Moreover, the graphical user interface displays such relationship, illustrating which locations within the event records are associated with which portion of the split timestamp information.

While the plurality of event records may be configured to include structured data having definable locations, such as fields, columns, or the like, based on separators, field headers, or so forth, subject innovations discussed herein are not limited to structured data event records. Selection of locations may also be performed over unstructured data event records. For example, in some embodiments, an analysis might be performed that provides extraction rules, or the like, that may identify locations within the unstructured data event records having time information. The event records may be displayed through the graphical user interface to enable the user to select locations over which to split the timestamp information.

It should be noted that while the subject innovations discussed herein disclose splitting timestamp information across locations within event records, the subject innovations are not constrained to timestamp information. Thus, in some embodiments, other splitting information might also employ similar selectors. For example, information about geographic regions might be split across various locations within event records, such as country information for one location within the event records, state or district information for another location within the event records, and city or town information for still another location within the event records. Virtually any information that can be split for use in identifying different locations within event records may be used.

Illustrative Operating Environment

FIG. 1shows components of an environment in which various embodiments may be practiced. Not all of the components may be required to practice the various embodiments, and variations in the arrangement and type of the components may be made without departing from the spirit or scope of the various embodiments.

In at least one embodiment, cloud network102enables one or more network services for a user based on the operation of corresponding arrangements104and106of virtually any type of networked computing device. As shown, the networked computing devices may include extraction rule server device112, event records server device114, enclosure of blade servers110, enclosure of server computers116, super computer network device118, and the like. Although not shown, one or more client devices may be included in cloud network102in one or more arrangements to provide one or more network services to a user. Also, these arrangements of networked computing devices may or may not be mutually exclusive of each other.

In at least one of the various embodiments, extraction rule server device112may include module, processes, components, services, or the like, for generating extraction rules for extracting fields from event records. Further, in at least one of the various embodiments, event records server device114may include processes, modules, services, components, or the like, for collecting and managing data event records. In at least one of the various embodiments, event records server device114may employ extraction rules provided by extraction rule server112for managing event records, or other forms of data.

Additionally, the user may employ a plurality of virtually any type of wired or wireless networked computing devices to communicate with cloud network102and access at least one of the network services enabled by one or more of arrangements104and106. These networked computing devices may include tablet client device122, handheld client device124, wearable client device126, desktop client device120, and the like. Although not shown, in various embodiments, the user may also employ notebook computers, server computers, microprocessor-based or programmable consumer electronics, network appliances, mobile telephones, smart telephones, pagers, radio frequency (RF) devices, infrared (IR) devices, Personal Digital Assistants (PDAs), televisions, integrated devices combining at least one of the preceding devices, and the like.

One embodiment of a client device is described in more detail below in conjunction withFIG. 3. Generally, client devices may include virtually any substantially networked computing device capable of communicating over a wired, wireless, or some combination of wired and wireless network.

In various embodiments, network102may employ virtually any form of communication technology and topology. For example, network102can include local area networks Personal Area Networks (PANs), (LANs), Campus Area Networks (CANs), Metropolitan Area Networks (MANs) Wide Area Networks (WANs), direct communication connections, and the like, or any combination thereof. On an interconnected set of LANs, including those based on differing architectures and protocols, a router acts as a link between LANs, enabling messages to be sent from one to another. In addition, communication links within networks may include virtually any type of link, e.g., twisted wire pair lines, optical fibers, open air lasers or coaxial cable, plain old telephone service (POTS), wave guides, acoustic, full or fractional dedicated digital communication lines including T1, T2, T3, and T4, and/or other carrier and other wired media and wireless media. These carrier mechanisms may include E-carriers, Integrated Services Digital Networks (ISDNs), universal serial bus (USB) ports, Firewire ports, Thunderbolt ports, Digital Subscriber Lines (DSLs), wireless links including satellite links, or other communications links known to those skilled in the art. Moreover, these communication links may further employ any of a variety of digital signaling technologies, including without limit, for example, DS-0, DS-1, DS-2, DS-3, DS-4, OC-3, OC-12, OC-48, or the like. Furthermore, remotely located computing devices could be remotely connected to networks via a modem and a temporary communication link. In essence, network102may include virtually any communication technology by which information may travel between computing devices. Additionally, in the various embodiments, the communicated information may include virtually any kind of information including, but not limited to processor-readable instructions, data structures, program modules, applications, raw data, control data, archived data, video data, voice data, image data, text data, and the like.

Network102may be partially or entirely embodied by one or more wireless networks. A wireless network may include any of a variety of wireless sub-networks that may further overlay stand-alone ad-hoc networks, and the like. Such sub-networks may include mesh networks, Wireless LAN (WLAN) networks, Wireless Router (WR) mesh, cellular networks, pico networks, PANs, Open Air Laser networks, Microwave networks, and the like. Network102may further include an autonomous system of intermediate network devices such as terminals, gateways, routers, switches, firewalls, load balancers, and the like, which are coupled to wired and/or wireless communication links. These autonomous devices may be operable to move freely and randomly and organize themselves arbitrarily, such that the topology of network102may change rapidly.

Network102may further employ a plurality of wired and wireless access technologies, e.g., 2nd (2G), 3rd (3G), 4th (4G), 5th(5G) generation wireless access technologies, and the like, for mobile devices. These wired and wireless access technologies may also include Global System for Mobile communication (GSM), General Packet Radio Services (GPRS), Enhanced Data GSM Environment (EDGE), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution Advanced (LTE), Universal Mobile Telecommunications System (UMTS), Orthogonal frequency-division multiplexing (OFDM), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access 2000 (CDMA2000), Evolution-Data Optimized (EV-DO), High-Speed Downlink Packet Access (HSDPA), IEEE 802.16 Worldwide Interoperability for Microwave Access (WiMax), ultra wide band (UWB), user datagram protocol (UDP), transmission control protocol/Internet protocol (TCP/IP), any portion of the Open Systems Interconnection (OSI) model protocols, Short Message Service (SMS), Multimedia Messaging Service (MMS), Web Access Protocol (WAP), Session Initiation Protocol/Real-time Transport Protocol (SIP/RTP), or any of a variety of other wireless or wired communication protocols. In one non-limiting example, network102may enable a mobile device to wirelessly access a network service through a combination of several radio network access technologies such as GSM, EDGE, SMS, HSDPA, and the like.

Enclosure of Blade Servers

FIG. 2Ashows one embodiment of an enclosure of blade servers200, which are also illustrated inFIG. 1. Enclosure of blade servers200may include many more or fewer components than those shown inFIG. 2A. However, the components shown are sufficient to disclose an illustrative embodiment. Generally, a blade server is a stripped down server computing device with a modular design optimized to minimize the use of physical space and energy. A blade enclosure can include several blade servers and provide each with power, cooling, network interfaces, input/output interfaces, and resource management. Although not shown, an enclosure of server computers typically includes several computers that merely require a network connection and a power cord connection to operate. Each server computer often includes redundant components for power and interfaces.

As shown in the figure, enclosure200contains power supply204, and input/output interface206, rack logic208, several blade servers210,212,214, and216, and backplane202. Power supply204provides power to each component and blade server within the enclosure. The input/output interface206provides internal and external communication for components and blade servers within the enclosure. Backplane208can enable passive and active communication of power, logic, input signals, and output signals for each blade server.

Illustrative Blade Server

FIG. 2Billustrates an illustrative embodiment of blade server250, which may include many more or fewer components than those shown. As shown inFIG. 2A, a plurality of blade servers may be included in one enclosure that shares resources provided by the enclosure to reduce size, power, and cost.

Blade server250may include processor252which communicates with memory256via bus254. Blade server250may also include input/output interface290, processor-readable stationary storage device292, and processor-readable removable storage device294. Input/output interface29) can enable blade server250to communicate with other blade servers, client devices, network devices, and the like. Interface290may provide wireless and/or wired communication links for blade server. Processor-readable stationary storage device292may include devices such as an electromagnetic storage device (hard disk), solid state hard disk (SSD), hybrid of both an SSD and a hard disk, and the like. Also, processor-readable removable storage device294enables processor252to read non-transitory storage media for storing and accessing processor-readable instructions, modules, data structures, and other forms of data. The non-transitory storage media may include Flash drives, tape media, floppy media, and the like.

Memory256may include Random Access Memory (RAM), Read-Only Memory (ROM), hybrid of RAM and ROM, and the like. As shown, memory256includes operating system258and basic input/output system (BIOS)260for enabling the operation of blade server250. In various embodiments, a general-purpose operating system may be employed such as a version of UNIX, or LINUX™, or a specialized server operating system such as Microsoft's Windows Server™ and Apple Computer's iOS Server™.

Memory256may further include one or more data storage270, which can be utilized by blade server250to store, among other things, applications280and/or other data. Data stores270may include program code, data, algorithms, and the like, for use by processor252to execute and perform actions. In one embodiment, at least some of data store270might also be stored on another component of blade server250, including, but not limited to, processor-readable removable storage device294, processor-readable stationary storage device292, or any other processor-readable storage device (not shown). Data storage270may include, for example, event records272, timestamp associations275, and extraction rules274. Timestamp associations275may include tags, labels, indices, tables, or other mechanisms usable to associate timestamp information with locations within event records.

Applications280may include processor executable instructions which, when executed by blade server250, transmit, receive, and/or otherwise process messages, audio, video, and enable communication with other networked computing devices. Examples of application programs include database servers, file servers, calendars, transcoders, and so forth. Applications280may include, for example, extraction rule application282, and timestamp labeler283. In some embodiments, timestamp labeler283may be configured to provide a graphical user interface usable to identify locations within an event record with splittable timestamp information. Timestamp labeler283is illustrated as a separate application, however, it should be understood that timestamp labeler283may operate within another application or be called through another application. Moreover, timestamp labeler283may employ a process such as described below in more detail in conjunction withFIG. 5to perform at least some of its actions. Timestamp labeler283may further employ graphical user interfaces, such as those discussed below in conjunction withFIGS. 6A-6C.

Human interface components (not pictured), may be remotely associated with blade server250, which can enable remote input to and/or output from blade server250. For example, information to a display or from a keyboard can be routed through the input/output interface290to appropriate peripheral human interface components that are remotely located. Examples of peripheral human interface components include, but are not limited to, an audio interface, a display, keypad, pointing device, touch interface, and the like.

Illustrative Client Device

FIG. 3shows one embodiment of client device300that may include many more or less components than those shown. Client device300may represent, for example, at least one embodiment of client devices shown inFIG. 1.

Client device300may include processor302in communication with memory304via bus328. Client device300may also include power supply330, network interface332, audio interface356, display350, keypad352, illuminator354, video interface342, input/output interface338, haptic interface364, global positioning systems (GPS) receiver358, open air gesture interface360, temperature interface362, camera(s)340, projector346, pointing device interface366, processor-readable stationary storage device334, and processor-readable removable storage device336. Client device300may optionally communicate with a base station (not shown), or directly with another computing device. And in one embodiment, although not shown, a gyroscope may be employed within client device300to measuring and/or maintaining an orientation of client device300.

Power supply330may provide power to client device300. A rechargeable or non-rechargeable battery may be used to provide power. The power may also be provided by an external power source, such as an AC adapter or a powered docking cradle that supplements and/or recharges the battery.

Audio interface356may be arranged to produce and receive audio signals such as the sound of a human voice. For example, audio interface356may be coupled to a speaker and microphone (not shown) to enable telecommunication with others and/or generate an audio acknowledgement for some action. A microphone in audio interface356can also be used for input to or control of client device300, e.g., using voice recognition, detecting touch based on sound, and the like.

Display350may be a liquid crystal display (LCD), gas plasma, electronic ink, light emitting diode (LED), Organic LED (OLED) or any other type of light reflective or light transmissive display that can be used with a computing device. Display350may also include a touch interface344arranged to receive input from an object such as a stylus or a digit from a human hand, and may use resistive, capacitive, surface acoustic wave (SAW), infrared, radar, or other technologies to sense touch and/or gestures.

Keypad352may comprise any input device arranged to receive input from a user. For example, keypad352may include a push button numeric dial, or a keyboard. Keypad352may also include command buttons that are associated with selecting and sending images.

Illuminator354may provide a status indication and/or provide light. Illuminator354may remain active for specific periods of time or in response to events. For example, when illuminator354is active, it may backlight the buttons on keypad352and stay on while the client device is powered. Also, illuminator354may backlight these buttons in various patterns when particular actions are performed, such as dialing another client device. Illuminator354may also cause light sources positioned within a transparent or translucent case of the client device to illuminate in response to actions.

Client device300may also comprise input/output interface338for communicating with external peripheral devices or other computing devices such as other client devices and network devices. The peripheral devices may include an audio headset, display screen glasses, remote speaker system, remote speaker and microphone system, and the like. Input/output interface338can utilize one or more technologies, such as Universal Serial Bus (USB), Infrared, WiFi, WiMax, Bluetooth™, and the like.

Haptic interface364may be arranged to provide tactile feedback to a user of the client device. For example, the haptic interface364may be employed to vibrate client device300in a particular way when another user of a computing device is calling. Temperature interface362may be used to provide a temperature measurement input and/or a temperature changing output to a user of client device300. Open air gesture interface360may sense physical gestures of a user of client device300, for example, by using single or stereo video cameras, radar, a gyroscopic sensor inside a device held or worn by the user, or the like. Camera340may be used to track physical eye movements of a user of client device300.

GPS transceiver358can determine the physical coordinates of client device300on the surface of the Earth, which typically outputs a location as latitude and longitude values. GPS transceiver358can also employ other geo-positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), Enhanced Observed Time Difference (E-OTD), Cell Identifier (CI), Service Area Identifier (SAI), Enhanced Timing Advance (ETA), Base Station Subsystem (BSS), or the like, to further determine the physical location of client device300on the surface of the Earth. It is understood that under different conditions, GPS transceiver358can determine a physical location for client device300. In at least one embodiment, however, client device300may, through other components, provide other information that may be employed to determine a physical location of the device, including for example, a Media Access Control (MAC) address, IP address, and the like.

Human interface components can be peripheral devices that are physically separate from client device300, allowing for remote input and/or output to client device300. For example, information routed as described here through human interface components such as display350or keyboard352can instead be routed through network interface332to appropriate human interface components located remotely. Examples of human interface peripheral components that may be remote include, but are not limited to, audio devices, pointing devices, keypads, displays, cameras, projectors, and the like. These peripheral components may communicate over a Pico Network such as Bluetooth™, Zigbee™ and the like. One non-limiting example of a client device with such peripheral human interface components is a wearable computing device, which might include a remote pico projector along with one or more cameras that remotely communicate with a separately located client device to sense a user's gestures toward portions of an image projected by the pico projector onto a reflected surface such as a wall or the user's hand.

Memory304may include RAM, ROM, and/or other types of memory. Memory304illustrates an example of computer-readable storage media (devices) for storage of information such as computer-readable instructions, data structures, program modules or other data. Memory304may store BIOS308for controlling low-level operation of client device300. The memory may also store operating system306for controlling the operation of client device300. It will be appreciated that this component may include a general-purpose operating system such as a version of UNIX, or LINUX™, or a specialized mobile computer communication operating system such as Windows Phone™, or the Symbian® operating system. The operating system may include, or interface with a Java virtual machine module that enables control of hardware components and/or operating system operations via Java application programs.

Memory304may further include one or more data storage310, which can be utilized by client device300to store, among other things, applications320and/or other data. For example, data storage310may also be employed to store information that describes various capabilities of client device300. The information may then be provided to another device based on any of a variety of events, including being sent as part of a header during a communication, sent upon request, or the like. Data storage310may also be employed to store social networking information including address books, buddy lists, aliases, user profile information, or the like. Data storage310may further include program code, data, algorithms, and the like, for use by a processor, such as processor302to execute and perform actions. In one embodiment, at least some of data storage310might also be stored on another component of client device300, including, but not limited to, non-transitory processor-readable removable storage device336, processor-readable stationary storage device334, or even external to the client device.

Applications320may include computer executable instructions which, when executed by client device300, transmit, receive, and/or otherwise process instructions and data. Applications320may include, for example, extraction rule application322. Other examples of application programs include calendars, search programs, email client applications, IM applications, SMS applications, Voice Over Internet Protocol (VOIP) applications, contact managers, task managers, transcoders, database programs, word processing programs, security applications, spreadsheet programs, games, search programs, and so forth.

Extraction rule application322may be configured to enable creation of extraction rules and to display results of the extraction rules to a user. In at least one embodiment, extraction rule application322may interact with and/or employed through a web browser. In some embodiments, embodiments, extraction rule application322may enable a user to input and/or edit one or more extraction rules. In other embodiments, extraction rule application322may display a plurality of event records to a user, values extracted from the event records using the extraction rule, statistics about the extracted values, or the like.

Also shown is timestamp labeler323, which is configured to enable client device300to display and use a graphical user interface to identify one or more locations within an event record that may have time information, and to further allow the locations to be associated with splittable timestamp information. Such splittable timestamp information may then be usable to perform any of a variety of time related actions upon the event records, including, but not limited to performing sorts on the event records, or locations within the event records; performing extractions of information within the event records or locations within the event records; or performing any of a variety of analysis on the event records.

While timestamp labeler323is illustrated as within extraction rule application322, this need not be the case in other embodiments, and thus should not be construed as limiting the subject innovations. For example, timestamp labeler323might operate as a separate application, called from another application, or even operate on another network device over a network. In some embodiments timestamp labeler323is configured to provide graphical user interfaces such as those discussed in more detail below in conjunction withFIGS. 6A-6C, and further employ a process such as discussed below in conjunction withFIG. 5.

Illustrative Network Device

FIG. 4shows one embodiment of network device400that may be included in a system implementing the invention. Network device400may include many more or less components than those shown inFIG. 4. However, the components shown are sufficient to disclose an illustrative embodiment for practicing the present invention. Network device400may represent, for example, one embodiment of at least one of network device112,114, or120ofFIG. 1.

As shown in the figure, network device400may include a processor402in communication with a memory404via a bus428. Network device400may also include a power supply430, network interface432, audio interface456, display450, keyboard452, input/output interface438, processor-readable stationary storage device434, processor-readable removable storage device436, and pointing device interface458. Power supply430provides power to network device400.

Network interface432may include circuitry for coupling network device400to one or more networks, and is constructed for use with one or more communication protocols and technologies including, but not limited to, protocols and technologies that implement any portion of the Open Systems Interconnection model (OSI model), GSM, CDMA, time division multiple access (TDMA), UDP, TCP/IP, SMS, MMS, GPRS, WAP, UWB, WiMax, SIP/RTP, or any of a variety of other wired and wireless communication protocols. Network interface432is sometimes known as a transceiver, transceiving device, or network interface card (NIC). Network device400may optionally communicate with a base station (not shown), or directly with another computing device.

Audio interface456is arranged to produce and receive audio signals such as the sound of a human voice. For example, audio interface456may be coupled to a speaker and microphone (not shown) to enable telecommunication with others and/or generate an audio acknowledgement for some action. A microphone in audio interface456can also be used for input to or control of network device400, for example, using voice recognition.

Display450may be a liquid crystal display (LCD), gas plasma, electronic ink, light emitting diode (LED), Organic LED (OLED) or any other type of light reflective or light transmissive display that can be used with a computing device. Display450may be a handheld projector or pico projector capable of projecting an image on a wall or other object.

Network device400also may also comprise input/output interface438for communicating with external devices not shown inFIG. 4. Input/output interface438can utilize one or more wired or wireless communication technologies, such as USB™, Firewire™, WiFi, WiMax, Thunderbolt™, Infrared, Bluetooth™, Zigbee™, serial port, parallel port, and the like.

Human interface components can be physically separate from network device400, allowing for remote input and/or output to network device400. For example, information routed as described here through human interface components such as display450or keyboard452can instead be routed through the network interface432to appropriate human interface components located elsewhere on the network. Human interface components can include any component that allows the computer to take input from, or send output to, a human user of a computer.

Memory404may include RAM, ROM, and/or other types of memory. Memory404illustrates an example of computer-readable storage media (devices) for storage of information such as computer-readable instructions, data structures, program modules or other data. Memory404may store BIOS408for controlling low-level operation of network device400. The memory may also store operating system406for controlling the operation of network device400. It will be appreciated that this component may include a general-purpose operating system such as a version of UNIX, or LINUX™, or a specialized operating system such as Microsoft Corporation's Windows® operating system, or the Apple Corporation's iOS® operating system. The operating system may include, or interface with a Java virtual machine module that enables control of hardware components and/or operating system operations via Java application programs.

Memory404may further include one or more data storage410, which can be utilized by network device400to store, among other things, applications420and/or other data. For example, data storage410may also be employed to store information that describes various capabilities of network device400. The information may then be provided to another device based on any of a variety of events, including being sent as part of a header during a communication, sent upon request, or the like. Data storage410may also be employed to store social networking information including address books, buddy lists, aliases, user profile information, or the like. Data stores410may further include program code, data, algorithms, and the like, for use by a processor, such as processor402to execute and perform actions. In one embodiment, at least some of data store410might also be stored on another component of network device400, including, but not limited to, non-transitory media inside processor-readable removable storage device436, processor-readable stationary storage device434, or any other computer-readable storage device within network device400, or even external to network device400.

Data storage410may include, for example, event records412and extraction rules416. In some embodiments, event records412may store data, including a plurality of event records. In at least one of various embodiments, event records412may be stored by event records server device114ofFIG. 1. Extraction rules416may include one or more extractions rules. These extraction rules may be automatically created based on a user selection of text, input by a user, and/or otherwise provided to the system. In at least one embodiment, extraction rules416may be stored and/or otherwise processed by extraction rule server device112ofFIG. 1. Further, data storage410may also include timestamp associations413, where such associations might include tags, labels, indices, tables, lists, or the like. However, in other embodiments, modifications might be made to event records stored within event records412to indicate timestamp associations, including, modifying event records to include tags, labels, headers, additional fields, field information, or the like.

Applications420may include computer executable instructions which, when executed by network device400, transmit, receive, and/or otherwise process messages (e.g., SMS, MMS, Instant Message (IM), email, and/or other messages), audio, video, and enable telecommunication with another user of another client device. Other examples of application programs include calendars, search programs, email client applications, IM applications, SMS applications, Voice Over Internet Protocol (VOIP) applications, contact managers, task managers, transcoders, database programs, word processing programs, security applications, spreadsheet programs, games, search programs, and so forth. Applications420may include, for example, extraction rule application422and timestamp labeler423.

Extraction rule application422may be configured to enable creation of extraction rules and to display results of the extraction rules to a user. In at least one embodiment, extraction rule application422may interact with a client device for enabling a user to input and/or edit one or more extraction rules. In other embodiments, extraction rule application422may enable a client device to display a plurality of event records to a user, values extracted from the event records using the extraction rule, statistics about the extracted values, or the like. In at least one embodiment, extraction rule application422may interact with event records412and/or extraction rules416to access and/or store event records and/or extraction rules, respectively. In some embodiments, extraction rule application422may be employed by extraction rule server device112ofFIG. 1.

Timestamp labeler423is configured to provide a graphical user interface usable to identify one or more locations within event records with splittable timestamp information. A display of a plurality of event records is provided to a user through the graphical user interface using any of a variety of formats, including those described below in conjunction withFIGS. 6A-C. A splittable timestamp selector is displayed within the graphical user interface that allows the user to select one or more locations within event records as having time related information that may be split across the one or more locations. The splittable timestamp information may then be associated with respective locations within the event records using any of a variety of mechanisms. The associations may be stored such that it may later be used by extraction rules, sort applications, and/or any of a variety of applications in which time information may be used. For example, timestamp labeler422might store the associations in event records412, and/or in timestamp associations413. Timestamp labeler424may employ a process such as described below in conjunction withFIG. 5.

General Operation

The operation of certain aspects of the invention will now be described with respect toFIG. 5.FIG. 5illustrates a logical flow diagram generally showing one embodiment of an overview process for identifying one or more locations within an event record with splittable timestamp information. Process500ofFIG. 5may be implemented within one or more client devices ofFIG. 1, blade server250ofFIG. 2B, and/or network device400ofFIG. 5.

Process500begins, after a start block, at block502, where a plurality of event records are received, and one or more of the event records are displayed using a graphical user interface (GUI). The GUI may be implemented using any of a variety of mechanisms, and is not constrained to any particular mechanism for displaying the one or more event records. In some embodiments, the GUI may be displayed to a user of a client device, such as described above in conjunction withFIGS. 1 and 3. However, the GUI may also be configured to be displayed using any of a variety of other devices as well. Moreover, the display of the one or more event records may use any of a variety of formats and/or arrangements. For example, event records may be displayed in a table format having rows and columns. In such a display, each event record displayed might be a displayed row, while fields or locations within the event record are columns. In other embodiments, each event record displayed might be a column, while fields or locations within the event records are rows. As discussed further below, other arrangements may also be used.

Process500then flows to block504, where the GUI also displays a splittable timestamp selector. The splittable timestamp selector might be represented as a pull down menu structure, a push button, a drag/drop selector, or any of a variety of other selector mechanisms, including a combination of one or more selector mechanisms. The splittable timestamp selector is configured to allow the user to identify locations within a displayed event record having portions of time information for which the user may select. For example, one location of the event record might include month/day/year information, while another location within the event record might include day of the week information, time of day information, or so forth. Clearly, an event record might include locations that include combinations of such time information, and/or other types of time information. Therefore, subject innovations are not limited to a particular structure, type, or combination of time information. Virtually any time information may be included for which a user might select.

In one non-limiting example, a user might identify locations within an event record having time information that is distributed across different fields or locations within an event record. For example, one field or location within an event record might include time of day information in the form of time that is local to a source of the event record, and another location that includes universal time of day information. Another location of the event record might include, however, month/day/year information. Thus, time information might be distributed across different locations within an event record. Some of these locations within the event record however might not include a label, tag, header, or other type of indication that the content includes time information. The user might therefore wish to identify such locations as having a particular type of time information. Using the splittable timestamp selector within the GUI, the user may drag, slide, or otherwise identify and select locations within the event record as having time information, and what type of time information. The splittable timestamp selector allows the user to split timestamp information across different locations within the event record. The GUIs discussed below in conjunction withFIGS. 6A-Cillustrate non-limiting examples of performing such selections.

Process500then moves to block506where as the user selects locations with split timestamp information, the splittable timestamp information is associated with the selected locations. This association may be accomplished using a variety of mechanisms. For example, a new field, header, tag, label, or the like might be automatically inserted in the event records, event record headers, or the like, that include the split timestamp information. However, in other embodiments, information about the selected locations might be inserted into a table, list, index structure, or the like, along with the associated split timestamp information. For example, the location within the event records might be identified as characters 26-31 and as having time information to be associated with the split timestamp of Month (2 characters), Day (2 characters), and Year (2 characters). Such information may be included in a table, list, index structure, or the like, that might be maintained separately, within another event record, or using any of a variety of other mechanisms.

Process500flows next to decision block508where a determination is made whether more splittable timestamp information is to be selected and associated with locations within the event records. If so, processing flows back to block504to continue until no more selections are performed. Processing then continues to optional block510.

At block510, a user may create an extraction rule that includes splittable timestamps within the rule. For example, the user might select event records where the MM/DD/YY time information, identified using the splittable timestamp, is greater than some value. As noted, any of a variety of other extraction criteria may be employed. As such, the subject innovations are not limited by this example. Proceeding to block512, the extraction rule having splittable timestamp information is then used to extract event records that satisfy the extraction rule. Continuing to block514, any of a variety of analyses might then be performed on the extracted event records.

Process500then flows to decision block516, where a determination is made whether to continue identifying and selecting locations within event records with splittable timestamp information. If so, processing branches back to block504; otherwise, processing may return to a calling process.

NON-LIMITING, NON-EXHAUSTIVE EXAMPLES OF GRAPHICAL USER INTERFACES

FIGS. 6A-Cillustrate various non-limiting, non-exhaustive graphical user interfaces usable for identifying/selecting one or more locations within event records with splittable timestamp information.

GUIs600A-C ofFIGS. 6A-Care directed towards providing examples of GUIs that may be used to display one or more event records and to select locations within the event records as having time information. The GUIs further display a splittable timestamp selector that may be used to select locations within the event records as having time information. The splittable timestamp selector may be used to identify the type of time information within the selected location. This splittable timestamp information may then be associated with the selected locations as discussed above.

GUI600A ofFIG. 6Aillustrates event records612-614, within section608A. Other sections within GUI600A may also be displayed, including, data source602, which indicates a source of the event records; extraction rule preview604, which may be used to create an extraction rule, and input606usable to enable the user to define a specific filter to apply to the event records (e.g., the user may filter the event records to display those event records that were recorded on a particular day). In other embodiments, input606may also enable a user to select how the event records are displayed.

As is further shown inFIG. 6A, event records612-614are displayed in a ‘by row’ format, where each row represents one event record. Also, shown as columns are locations630-637for each of event records612-614. Where tags, labels, or field headers are available, they are further illustrated in row610.

Splittable timestamp selector620is shown inFIG. 6A, having selection arrows that may be employed to select split time information. Splittable timestamp selector620may be clicked on, dragged, or otherwise moved, relocated over one or more columns/locations of the displayed event records612-614to select a location having time information. The selection arrows may be used to select a split time for the selected location. In one non-limiting, non-exhaustive example, a user might drag splittable timestamp selector620over location631and employ the selection arrows to identify that location631has month/day/year (MM/DD/YY) time information. A result of such actions is shown as splittable timestamp selection621. Similar actions may be repeated, resulting in splittable timestamp selection622showing location633having time of day, in Zulu time; and splittable timestamp selection623showing location636having weekday time information. Thus, using GUI600A, the user may employ splittable timestamp selector620multiple times, to select multiple locations within the displayed event records as having split time information. However, in other embodiments, splittable timestamp selection621might be dragged to another location to enable splitting of, for example, the MM/DD/YY time information. Thus, in some embodiments, a user might split the MM/DD/YY time information across two or more locations, such as MM for one location, DD for another location, and YY for still another location. Similarly, splittable timestamp selection622might also be further split. Thus, in some embodiments, the splittable timestamp selection622might be dragged over multiple locations, with selections made using splittable timestamp selection622as sort of an extension of splittable timestamp selector620. Thus, in this manner, designating splits of time across locations within event records may be performed in a variety of ways.

It should be clear that any of a variety of other locations, and/or split time information may be selected. For example, in one embodiment, splittable timestamp selector620might allow a user to select to enter a definition of split time for locations. That is, in some embodiments, the user might define a unique splitting of time, or even a previously undefined timestamp designation. Moreover, in some embodiments, when a location within the displayed event records is selected, an association is made between the split time information and the selected location to indicate that the selection location has time information as indicated by the selected identifier (e.g., MM/DD/YY, time of day: Zulu, or weekday). Moreover, it should be understood that such association between the split time information and the location might be applied over a plurality of event records, including those event records that are displayed, or alternatively, over a subset of event records, such as event records extracted from the plurality of event records based on an extraction rule, or the like. In any event, the splittable timestamp/location associations may then be used to perform any of a variety of operations upon the event records.

As noted above, subject innovations are not limited by how an event record, event record locations, and splittable timestamp information is displayed, Thus, whileFIG. 6Aillustrates event records612-614in rows, and columns as locations/fields within the event records, other arrangements may be used. For example, in some embodiments, event records might be displayed in columns, while locations/fields with the event records might be displayed in rows. Splittable timestamp information may then be displayed in a column, and aligned with respectively selected locations/rows within the event records.

For example, some data might have event records with too many extracted fields to readily display as columns. Therefore, in some embodiments, the fields of each event record might be displayed with one field per row for each event record, and then displaying event records one under another. A similar concept might include moving the splittable timestamp information between fields to indicate the one from which a timestamp might be extracted, or otherwise selected; however, in this instance the timestamp (or portions thereof) might move up or down between the fields rather than across columns.

FIG. 6Bshows still another non-limiting, non-exhaustive arrangement of event records, locations/fields within event records, and how splittable timestamp information might be displayed. In this example, GUI600B shows portions of event records612-613. The event records are shown in a single column, one event record below another event record. Shown for event record612are locations631A and633A, while at least location631B of event record613is displayed. A scrolling tool is shown next to each event record, allowing scrolling within each event record, to display respective locations/fields within an event record. Moreover a global scrolling tool is shown that allows for scrolling over the event records. Splittable timestamp selector620may again be used to select locations within the displayed event records as having time information, as discussed above. Thus, as shown,FIG. 6Bshows results of a selection of field/location631A as having split time information of MMDDYY, as shown by splittable timestamp selection621A. In some embodiments, such selection in one event record may be automatically reflected within other event records. Thus, in some embodiments, splittable timestamp selection621B might automatically be displayed to reflect selections of a similar field/location within another event record based one selection. Also shown is splittable timestamp selection622A for location633A of event record612. While not displayed, a similar automatic selection might occur for event record613, and/or other event records.

FIG. 6Cillustrates still another non-limiting, non-exhaustive arrangement of event records, locations/fields within event records, and how splittable timestamp information might be displayed. In this example, GUI600C, event records are again displayed in row format, as in612A,613A, and so forth. However, a separate row is also shown for fields/locations selected as having time information. Thus, as shown row641illustrates that field 1 (location631) of the event records612-613(as displayed by event records612A and613A) has time information as shown by splittable timestamp selection621. Similarly, row641also shows that field 3 (location633) of the event records612-613(and displayed as event records612B and613B) has time information as shown by splittable timestamp selection622. In this example, then, GUI600C might display multiple instances of an event record, as rows, with other rows indicating which field/location within the event records are selected using the splittable timestamp selector620.

Other arrangements or structures, formats, or the like, may be used to display within a GUI event records and locations within the event records such that a user might select locations having time information using a splittable timestamp selector. Thus, embodiments should not be construed as being limited by any particular arrangement of event records, type of splittable timestamp selectors, or mechanisms used to select locations within event records.