The disclosed apparatus, systems, and methods relate to a location query mechanism that can efficiently determine whether a target entity is located within a region of interest (ROI). At a high level, the location query mechanism can be configured to represent a ROI using one or more polygons. The location query mechanism can, in turn, divide (e.g., tessellate) the one or more polygons into sub-polygons. Subsequently, the location query mechanism can use the sub-polygons to build an index system that can efficiently determine whether a particular location is within any of the sub-polygons. Therefore, when a computing device queries whether a particular location is within the region of interest, the location query mechanism can use the index system to determine whether the particular location is within any of the sub-polygons.

Embodiments are directed towards a graphical user interface 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 or the event records.

Streaming data, such as streaming records transmitted from entities, can be managed. For example, a new record associated with an entity can be received. There can be an existing record for the entity within a group of records. The group of records can form a block. A new block for the new record can be generated. A datastore can be updated to indicate that the new block has the most current record for the entity. Entries in the datastore can be filtered to identify a subgroup of blocks that has the most current record for each entity of multiple entities. A combined group of blocks can be generated by joining the new block with the subgroup of blocks. The combined group of blocks can be processed as a batch of data by a processing engine.

Various systems and methods are provided for performing soft entity resolution. A plurality of data objects are retrieved from a plurality of data stores to create aggregated data objects for one or more entities. One or more retrieved data objects may be associated with the same entity, based at least in part upon one or more attribute types and attribute values of the data objects. In response to a determination that the one or more of the retrieved data objects should be associated with the same entity, metadata is generated that associates the data objects with the entity, the metadata being stored separately from the data objects, such that the underlying data objects remain unchanged. In addition, one or more additional attributes may be determined for the entity, based upon the data objects associated with the entity.

In some embodiments, the present disclosure provides for an exemplary computer-implemented system that may include a longitudinal data engine, including: a processor and specialized index generation software to generate: an index data structure for a respective event type associated with each respective subject or object; where each respective index data structure is a respective event type-specific data schema, defining how to store events of a particular event type to form longitudinal data of each respective subject or object; an ontology data structure that is configured to describe one or more properties of a respective event of a respective subject or object; and longitudinal data extraction software to extract a respective longitudinal data for a plurality of index data structures and a plurality of ontology data structures associated with a plurality of subjects or objects.

Disclosed are systems and methods for monitoring user-defined metrics. A method may include: receiving, from a user device, a metric definition usable to generate queries to obtain data for a metric to be monitored; receiving, from the user device, a monitoring configuration indicative of a manner in which a metric monitoring process associated with the metric definition is to be repeatedly performed; storing the metric definition in a metric definition database; and repeatedly performing the metric monitoring process in accordance with the monitoring configuration. The metric monitoring process may include: retrieving the metric definition from the metric definition database; generating a database query based on the metric definition, the database query including one or more executable database statements defined by the metric definition; executing the database query to obtain query result data, the query result data being data for the metric; and storing the query result data.

A method is disclosed that includes receiving a request to display a service-monitoring user interface that illustrates performance of one or more services that are each provided by one or more entities. Each service is associated with a stored service definition that identifies the one or more entities, and each entity is associated with stored entity definition information that identifies machine data produced by or about the entity from one or more sources. The method further includes causing display of the service-monitoring user interface illustrating performance of each service via an aggregate key performance indicator (KPI) that characterizes a respective service as a whole, and a plurality of aspect KPIs that each characterize an aspect of an associated service. Each KPI is defined by a search query that produces a value derived from the machine data identified by the entity definition information, the value indicative of a measure of the service at a point in time or during a period of time. The machine data is produced by one or more components within an information technology environment and reflects activity within the information technology environment.

Artifact life tracking storage techniques include performing an artifact request of an artifact at an artifact storage node. A current time to live (TTL) value is identified. A determination is made whether to increment a TTL flag of the artifact. Responsive to determining that the TTL tag should be incremented, the TTL flag is incremented to a subsequent value in a TTL extender list. Responsive to incrementing the TTL tag, the TTL modified tag value is set to the current time value.

A method and system for accessing updated data from a database in response to a user query has been developed. First, multiple transaction logs are generated for a database. Each transaction log contains a record of actions executed by a database management system and referenced according to the specified date of the actions. Data updates are received and stored with the database. An incremental database partition is created for each data update. Each incremental database partition is stored with reference to a corresponding transaction log for the date of the data update. The updated data is accessed through the incremental database partition in response to an outdated user query. The outdated user query contains a data access request for a date earlier than the receipt of data updates.

A system and method for crowdsourced innovation and automated process implementation, wherein individuals and businesses use a distributed computational graph module with crowdsourcing-technology to develop ideas and create process workflows for implementing those ideas. The developed process workflows are implemented through a system which automatically integrates heterogenous Internet resources such as electronic commerce, recruiting, and management platforms into a single portal. Businesses and other collaboration initiatives are supported via crowdsourced labor that are automatically orchestrated by the distributed computational graph workflows and user interface that provide a comprehensive and convergent solution for process management.