Monitoring Splunk

How can I trace back to the search that generated splunkd.log searchParser errors?

lorenzo
New Member

Hello everyone,

I'm monitoring my Splunk Enterprise instance and, by looking at splunkd logs both via cli and search through:

index=_internal source="/opt/splunk/var/log/splunk/splunkd.log" log_level=ERROR

 

I find numerous SearchParser errors, namely the following one:

ERROR SearchParser [20709 TcpChannelThread] - Missing a search command before '|'. Error at position '2' of search query '| |'.

 

How can I trace back to the search that generated such error (either the search or the sid is fine)? Is that "20709" something of interest in this scenario?

Labels (3)
0 Karma
Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...