Splunk Search

Finding substrings

sloshburch
Splunk Employee
Splunk Employee

When searching for

index=myindex exception

I only get events with the text "exception" surrounded by term separators. Does anyone have any tips for how to also end up getting events with text like "this.is.AnExceptionEvent".

The only way I can think of is to search for "*exception*" but that ends up taking forever because of the massive amount of data that must be searched.

Can anyone spot any trick I've overlooked?

Tags (1)
1 Solution

martin_mueller
SplunkTrust
SplunkTrust

Searching for *exception* is the way to go, and you're right that it'll take ages. That's because using a wildcard at the beginning of a search phrase kills any chance of looking that up in the index structures. Instead, Splunk has to churn through all the raw data... that's regardless of whether you search for *exception* or field=*exception* in case of search time extraction.

I see two "tricks" you can try. See if there are other identifying keywords for your exception events. If there is, add those to your search to see it speed up massively.
If that's not the case you can consider extracting that field at index time. You'll add a bit of processing overhead to the indexer, but if you search for that field frequently you get that back many times over.

View solution in original post

martin_mueller
SplunkTrust
SplunkTrust

Searching for *exception* is the way to go, and you're right that it'll take ages. That's because using a wildcard at the beginning of a search phrase kills any chance of looking that up in the index structures. Instead, Splunk has to churn through all the raw data... that's regardless of whether you search for *exception* or field=*exception* in case of search time extraction.

I see two "tricks" you can try. See if there are other identifying keywords for your exception events. If there is, add those to your search to see it speed up massively.
If that's not the case you can consider extracting that field at index time. You'll add a bit of processing overhead to the indexer, but if you search for that field frequently you get that back many times over.

sloshburch
Splunk Employee
Splunk Employee

Thanks for elaborating. That's what I feared but I was optimistic that maybe I overlooked something trivial. Looks like we're all on the same page. Thanks!

0 Karma

sloshburch
Splunk Employee
Splunk Employee

I know what you mean. I have the message payload in a field but that still seems to be a slog because its a massive amount of data.

0 Karma

aweitzman
Motivator

Is the text extracted into a known field? Searching for field="*exception*" instead of just *exception* tends to be faster.

0 Karma
Get Updates on the Splunk Community!

Index This | Divide 100 by half. What do you get?

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

Stay Connected: Your Guide to December Tech Talks, Office Hours, and Webinars!

❄️ Celebrate the season with our December lineup of Community Office Hours, Tech Talks, and Webinars! ...

Splunk and Fraud

Watch Now!Watch an insightful webinar where we delve into the innovative approaches to solving fraud using the ...