CARVIEW |
Select Language
HTTP/2 200
date: Wed, 30 Jul 2025 23:59:46 GMT
content-type: text/html; charset=UTF-8
server: Apache
set-cookie: Apache=3388c36d.63b2e51bc7b20; path=/; expires=Thu, 26-Jul-40 23:59:46 GMT; domain=.splunk.com
x-frame-options: SAMEORIGIN
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-content-type-options: nosniff
set-cookie: PHPSESSID=5bd87440604da8f5c9ba47b2d60d9838; path=/
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
set-cookie: ponydocs_session=5bd87440604da8f5c9ba47b2d60d9838; path=/; secure; HttpOnly
x-xss-protection: 1; mode=block
referrer-policy: strict-origin-when-cross-origin
Splexicon:Parsing - Splunk Documentation
We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website.
Learn more (including how to update your settings) here »
parsing
parsing
noun
The second segment of the data pipeline. Data arrives at this segment from the input segment. This segment is where event processing occurs (where Splunk Enterprise analyzes data into logical components).
After data is parsed, it moves to the next segment of the pipeline, indexing.
Parsing of external data can occur on either an indexer or a heavy forwarder.
Parsing can also occur on other components under limited circumstances:
- Various components, such as search heads and indexer cluster master nodes, process their own internal data. When doing so, they perform parsing locally.
- When a universal forwarder ingests structured data, it performs the parsing locally. The indexer does not further parse the structured data.
For more information
In the Distributed Deployment Manual:
In Getting Data In:
A
B
C
D
E
F
I
K
L
M
P
R
S
- saved search
- scheduled alert
- scheduled report
- scheduled search
- scheduler
- scripted authentication
- scripted input
- search
- search affinity
- Search app
- search artifact
- search assistant
- search execution directive
- search factor
- search field
- search filter
- search head
- search head cluster
- search head cluster captain
- search head cluster member
- search head clustering
- search head pooling
- search head targeting
- search job
- Search Job Inspector
- search macro
- search management
- search mode
- search peer
- search peer replication
- Search Processing Language
- search scheduler
- search time
- search timeline
- search view
- searchability
- searchable
- segment
- send to background
- sequence template
- series
- server
- server class
- Settings
- SignalFlow
- SignalFx Smart Agent receiver
- Simple XML
- single-instance deployment
- single-site indexer cluster
- SmartStore
- source
- source type
- span
- span tag
- SPL
- SPL2
- SPL2 statement
- Splunk Answers
- Splunk Distribution of OpenTelemetry Collector
- Splunk OpenTelemetry Collector
- Splunk platform
- Splunk UI
- Splunk Web
- Splunk Web Framework
- Splunkbase
- splunkd
- SplunkJS Stack
- stack mode
- standalone search head
- stanza
- static captain
- streaming command
- subsearch
- summary index
T
Closing this box indicates that you accept our Cookie Policy.