Processing Node Mapping for Flexible Search-Time Data Retrieval

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge of efficiently managing and analyzing vast amounts of diverse machine data generated by IT environments, including structured, semi-structured, and unstructured data, is exacerbated by the discarding of minimally processed data during preprocessing, limiting the flexibility and efficiency of data analysis.

Innovation Solution

A data intake and query system utilizing a late-binding schema and event-based processing, where events are stored and analyzed at search time, enabling flexible schema development and field-searchable data retrieval, with components like forwarders, indexers, and search heads to manage and process data efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If data is preprocessed and only specified data items are extracted for storage, then data retrieval efficiency is improved, but data analysis flexibility is reduced

Engineering Contradiction:
Improvedata retrieval efficiencyVSAvoiddata analysis flexibility
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary actions by collecting and storing event data in a standardized format with metadata during the data intake phase, but delays the actual schema binding and detailed processing until search time. This allows efficient data collection while preserving flexibility for various analysis needs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements dynamic schema binding where the data structure and processing logic are determined at search time rather than being fixed during data collection. This allows the system to adapt to different analysis requirements dynamically without requiring predefined schemas for all possible query types.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If minimally processed data is stored for later analysis, then data analysis flexibility is improved, but data processing complexity increases

Engineering Contradiction:
Improvedata analysis flexibilityVSAvoiddata processing complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the data processing workflow into distinct phases: data collection with minimal processing, data storage in standardized format, and schema binding/processing at search time. This segmentation allows each phase to be optimized independently, reducing overall complexity while maintaining flexibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary layer of event data with standardized metadata that sits between raw data collection and final analysis processing. This intermediary structure provides a flexible foundation that can be processed in multiple ways depending on the specific analysis needs without requiring complex preprocessing for each scenario.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of information

If vast amounts of diverse data are stored from multiple data systems, then data analysis insight potential is improved, but data search and analysis performance deteriorates

Engineering Contradiction:
Improvedata analysis insight potentialVSAvoiddata search and analysis performance
Core Design Contradiction:
Loss of informationVSSpeed

Solution Approach 1:

The system performs preliminary organization of diverse data into a standardized event format with consistent metadata structures during data collection, but delays detailed processing and schema binding until search time. This allows comprehensive data collection from multiple sources while maintaining search performance through efficient data organization.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system changes the processing parameters dynamically based on the specific search query and data type. Different data sources and query types can utilize different processing approaches and schema bindings, allowing optimal performance for each specific analysis scenario while maintaining the ability to handle diverse data types.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20260087017A1Searching data based on processing node map identifiers
Publication Date: 2026.03.26 CISCO TECHNOLOGY INC
  • US20260087017A1 patent drawing
  • US20260087017A1 patent drawing
  • US20260087017A1 patent drawing

AI summary

A data intake and query system can manage the search of large amounts of data using one or more processing nodes. When a new processing node is added or becomes available, the node coordinator can reassign duties from one or more processing nodes to the new processing node. The node coordinator can initially assign the new processing node one or more groups of data for backup purposes. At a later time, the node coordinator can reassign the new processing node to the one or more groups of data for searching purposes.