MENU
Which commands can run on both search heads and indexers?
In Splunk's processing model, commands are categorized based on how and where they execute within the search pipeline. Understanding these categories is crucial for optimizing search performance.
Distributable Streaming Commands:
Definition: These commands operate on each event individually and do not depend on the context of other events. Because of this independence, they can be executed on indexers, allowing the processing load to be distributed across multiple nodes.
Execution: When a search is run, distributable streaming commands can process events as they are retrieved from the indexers, reducing the amount of data sent to the search head and improving efficiency.
Examples: eval, rex, fields, rename
Other Command Types:
Dataset Processing Commands: These commands work on entire datasets and often require all events to be available before processing can begin. They typically run on the search head.
Centralized Streaming Commands: These commands also operate on each event but require a centralized view of the data, meaning they usually run on the search head after data has been gathered from the indexers.
Transforming Commands: These commands, such as stats or chart, transform event data into statistical tables and generally run on the search head.
By leveraging distributable streaming commands, Splunk can efficiently process data closer to its source, optimizing resource utilization and search performance.
Splunk Documentation: Types of commands