Splunk Search

Search for data in different indexes and only return data is ip filed is same in both

jrprez1804
Path Finder

index=notable |rename src as ip | stats count by ip
| JOIN type=inner ip [search index="abcd" "tags.Dev:"cluster1 OR index="abcd" "tags.Dev:"=cluster2
| stats count by ip]

if ip is in notable index and cluster1 return ip AND if ip in notable index and cluster2 return ip

Tags (2)
0 Karma
1 Solution

to4kawa
Ultra Champion
index=notable OR (index="abcd" ("tags.Dev:"cluster1 OR "tags.Dev:"=cluster2))
| eval ip=coalesce(src,ip) 
| stats count dc(index) as flag by ip 
| where flag > 1

Hi, @jrprez1804
This query searches two indexes and tallies by each ip.
That time, it is checked the indexes where the ip belongs.
and Excludes ips that belongs one index.

How about this?

View solution in original post

0 Karma

to4kawa
Ultra Champion
index=notable OR (index="abcd" ("tags.Dev:"cluster1 OR "tags.Dev:"=cluster2))
| eval ip=coalesce(src,ip) 
| stats count dc(index) as flag by ip 
| where flag > 1

Hi, @jrprez1804
This query searches two indexes and tallies by each ip.
That time, it is checked the indexes where the ip belongs.
and Excludes ips that belongs one index.

How about this?

0 Karma

adonio
Ultra Champion

hello there,

first, you can always do something like that: index=notable | stats count by src as ip_count | rename src as ip which will perform much better.
but now for your join question.
there are couple (or more) ways to achieve, but the overall idea is to first bring all the results to one place with a wider search, and then slice and dice as you wish. for example:

(index=notable src=*) OR (index="abcd" "tags.Dev:"cluster1 OR index="abcd" "tags.Dev:"=cluster2)
| eval normalized_ip = coalesce(ip,src)
| stats dc(index) as unique_indexes by normalized_ip
| where unique_indexes > 1

play around with the data after you capture all of it, and suite yourself with the approach you like. there are many ways to go about this one...

hope it helps

0 Karma

to4kawa
Ultra Champion

If I was thinking about the explanation, I was late.
The way is the same. 🙂

0 Karma
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

Splunk is officially part of Cisco

Revolutionizing how our customers build resilience across their entire digital footprint.   Splunk ...

Splunk APM & RUM | Planned Maintenance March 26 - March 28, 2024

There will be planned maintenance for Splunk APM and RUM between March 26, 2024 and March 28, 2024 as ...