Splunk Pipeline Explorer

Follow data from source acquisition to searchable buckets.

0 stages
10 components
64 failures
Capacity modelParallel ingestion pipeline sets

Add a second input/output lane. Heavy forwarders and indexers also duplicate their full parsing path.

server.conf[general] parallelIngestionPipelines = 1Select a component to model a second set.

Complete processing model

Select a component or topology to isolate the stages that participate.

RunsConditionalNot used
PipelineStageConfigurationDeployment ServerSyslog ServerHECSQL DatabaseDB ConnectUFHFIngest ProcessorIndexerAWS S3

Custom topology builder

Build 158

Model event data, fleet management and interactive user access independently. Authentication links never carry telemetry.

Custom route · 4 componentsDrag onto a component to connect · drop on blank space for a route entry
100%
Event dataFleet managementInteractive logon
Pan drag blank space · Zoom wheel · Fit 0
✓
Valid end-to-end pathComponent handoffs and destination ownership are consistent.
0 issues
Change historyCurrent browser session · newest first
No matching stages
Try another component, pipeline, or search term.