Splunk Search

Can I search without using join?

mcaulsc
Path Finder

Hi,
I'm looking to improve performance and avoid the subsearch_maxout issue with a join on two source types.

I'm joining on a one to many field 'Correlator', srctypeA has will have one unique entry for 'Correlator' and srctypeB has multiple entries. So when my search on srctypeA returns a value for Correlator I want to timechart by a field in records with matching Correlator in srctypeB.

So the current search below works, I'm looking for better performing options if anyone has any suggestions.

index=index1 sourcetype=srctypeA field1=ABC* 
| join max=0 type=inner Correlator [ search index=index1 sourcetype=srctypeB ]
| timechart span=1d count by field2 
Labels (2)
0 Karma

isoutamo
SplunkTrust
SplunkTrust
0 Karma

mcaulsc
Path Finder

thanks,
thats is what I have been attempting and I get to the stats point ok with 121k events returned but trying to get the data into a timechart is eluding me at the moment.  

0 Karma

isoutamo
SplunkTrust
SplunkTrust

Join has those limits (size of result set and timeout), which probably hits in your case.

Have you try Woodcock’s inner join example with stats and where? I suppose that it should help you.

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...