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
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...