Splunk Enterprise

How to include two index events without using JOIN command?

super_saiyan
Communicator

Hi Splunkers,

There is one field is common in 2 indexes. Using that field how can i co-relate and make a table out of it without using JOIN, Append & Appendpipe command ? Because those command will take a lot of time and 

Please refer to the below pictures

 

Thanks & regards

Labels (1)
Tags (2)
0 Karma
1 Solution

kamlesh_vaghela
SplunkTrust
SplunkTrust

@super_saiyan 

Can you please try this?

index=IDX1 OR index=IDX2 | stats values(User_IP) as User_IP,values(Action) as Action, values(Comments) as Comments by ID

 

Change the index name and field name as per your requirement.


KV

AKA- GOKU

 

View solution in original post

kamlesh_vaghela
SplunkTrust
SplunkTrust

@super_saiyan 

Can you please try this?

index=IDX1 OR index=IDX2 | stats values(User_IP) as User_IP,values(Action) as Action, values(Comments) as Comments by ID

 

Change the index name and field name as per your requirement.


KV

AKA- GOKU

 

super_saiyan
Communicator

But there is only one problem.
I am getting multiple comments values in a single table events.

Can we segregate that as well ?

@kamlesh_vaghela 

0 Karma

super_saiyan
Communicator

Are you a magician?

Because your magic spell(SPL) actually worked without giving any errors.

 

Thanks much 

0 Karma

kamlesh_vaghela
SplunkTrust
SplunkTrust

@super_saiyan 

Glad to help you.  😀 . If the solution resolved your problem then please accept the answer to the close question.

KV

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