Splunk Search

Disabling eventtypes on a per-query basis?

sowings
Splunk Employee
Splunk Employee

I've got a long-running search that's spending more time than necessary in command.search.typer. I say more time than necessary because I'm not referencing the eventtypes at all, whether as a field nor as part of my search string. I've tried the fields - eventtype strategy listed here, but I still see time spent in command.search.typer.

Anything else I can try to temporarily disable eventtypes?

(Splunk version is 4.3.6.)

Tags (1)
1 Solution

_d_
Splunk Employee
Splunk Employee

I suppose you can always do ...| fields [list of necessary fields ONLY] | ....

View solution in original post

_d_
Splunk Employee
Splunk Employee

I suppose you can always do ...| fields [list of necessary fields ONLY] | ....

sowings
Splunk Employee
Splunk Employee

Once I limited the search to just the fields I wanted, typer doesn't show up in job inspector. Thanks!

0 Karma

_d_
Splunk Employee
Splunk Employee

try this:

| fields - eventtype, tag::eventtype

0 Karma

sowings
Splunk Employee
Splunk Employee

Sadly, that doesn't work, either.

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!

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 ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...