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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Introduction to Splunk AI

How are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. Lucky for ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Maximizing the Value of Splunk ES 8.x

Splunk Enterprise Security (ES) continues to be a leader in the Gartner Magic Quadrant, reflecting its pivotal ...