Splunk Search

Help debugging job inspector data

gesman
Communicator

When i run search:
index=my_summary sourcetype=stash ip=13.13.137.13 | head 5

Job inspector's "normalizedSearch" as well as "remoteSearch" shows this:

litsearch index=my_summary sourcetype=stash ( ( ( sourcetype=access_combined_wcookie ) AND ( ( clientip="13.13.137.13" ) ) ) OR ( ( sourcetype=mnxxx ) AND ( ( vxxxIP="13.13.137.13" ) ) ) OR ( ( sourcetype=ncxxx ) AND ( ( SUBJECT_IP="13.13.137.13" ) ) ) ) OR ( ip="13.13.137.13" ) | litsearch index=my_summary sourcetype=stash ip=13.13.137.13 | fields keepcolorder=t "*" "_bkt" "_cd" "_si" "host" "index" "linecount" "source" "sourcetype" "splunk_server" | prehead limit=5 null=false keeplast=false

  1. Why litsearch looking for other sourcetypes I did not explicitly requested?
  2. Why litsearch query seemingly appears twice running similar query?
  3. How to judge the performance of query from job Inspector's data (besides using runDuration value)?
Tags (2)
0 Karma

dominiquevocat
SplunkTrust
SplunkTrust

Um, maybe limiting search commands in one of the roles you have?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...