Splunk Search

Merging two data sources

keishamtcs
Explorer

Hi..

Need some help in merging two search result.

i have one source with below result as such -

CommonIndex host Max
WinUnix appdcos 23.10
WinUnix hpmail 91.80

Another search result with output as such -

CommonIndex host Max
WinUnix ADDS 20.25
WinUnix BCMP 75.16

How can i reproduce the results like below in a single table. I have tried join,append but output is not correct.

CommonIndex host Max
WinUnix appdcos 23.10
WinUnix hpmail 91.80
WinUnix ADDS 20.25
WinUnix BCMP 75.16

Tags (2)
0 Karma
1 Solution

thambisetty
SplunkTrust
SplunkTrust

Hi,
try something like below,

index=a | table CommonIndex host Max | append [|search index=b | table CommonIndex host Max]

if fields are common in two indexes. you can try something like below,

index=a OR index=b | table CommonIndex host Max
————————————
If this helps, give a like below.

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust

It would help to see your two searches, but the general way to do it is to merge the two queries. You shouldn't need to use append or join.

(index=index1 sourcetype=st1) OR (index=index1 sourcetype=st2) | ... | table ComminIndex host Max
---
If this reply helps you, Karma would be appreciated.

thambisetty
SplunkTrust
SplunkTrust

Hi,
try something like below,

index=a | table CommonIndex host Max | append [|search index=b | table CommonIndex host Max]

if fields are common in two indexes. you can try something like below,

index=a OR index=b | table CommonIndex host Max
————————————
If this helps, give a like below.
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 ...