Splunk Search

issue with transactions

castle1126
Communicator

I had previously posted this question earlier: http://answers.splunk.com/questions/9264/am-i-bumping-into-limits-issue-with-subsearch-results. I've done some deeper digging and I believe I'm having a general issue with transactions.

I've done a simple search over an index for a 15 minute window and come up with 75,000 events returned. When I run a simple search to build the transactions (index=smtp [search index=smtp | fields + messageid] | transaction messageid) I end up receiving the same error:

Error in 'UnifiedSearch': Unable to parse the 'The specified search is too large. Please try to simplify your search.

What can be done to help resolve this issue?

Thanks!

Tags (1)
0 Karma
1 Solution

southeringtonp
Motivator

It doesn't look like the subsearch is really needed here, since all it appears to be doing is making sure that the messageid field is populated.

How about just:

index=smtp messageid=* | transaction messageid

View solution in original post

southeringtonp
Motivator

It doesn't look like the subsearch is really needed here, since all it appears to be doing is making sure that the messageid field is populated.

How about just:

index=smtp messageid=* | transaction messageid

castle1126
Communicator

Thanks much! Doing the search that way worked very nicely...

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!

Automated Threat Analysis: Available in ES Premier

Automated Threat Analysis: Centralize and Accelerate Phishing Investigations in Splunk Enterprise ...

What’s New in Splunk AI: Volume 02

Welcome to the second edition of “What’s New in Splunk AI” where we look at the latest and greatest updates, ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...