Splunk Search

How to compare to a lookup table and pull fields?

mgrosholz
Path Finder

I have an index=foo and a lookup table defined as foo2. How can I compare my index to the table to show only results matching fieldA in foo2 and pulling fieldB from foo2?

I have tried below and many variations of it but I get no results.

index=foo
[| inputlookup foo2 | fields fieldA]

index=foo
| lookup foo2 fieldA OUTPUT fieldB
Tags (1)
0 Karma
1 Solution

chrishartsock
Path Finder

Ultimately, you should be able to do:

index=foo
| lookup foo2 fieldA AS fieldA_name_in_foo OUTPUT fieldB
| where NOT isnull(fieldB)

View solution in original post

0 Karma

chrishartsock
Path Finder

Ultimately, you should be able to do:

index=foo
| lookup foo2 fieldA AS fieldA_name_in_foo OUTPUT fieldB
| where NOT isnull(fieldB)

0 Karma

mgrosholz
Path Finder

Why did you add the not null for fieldB?

0 Karma

chrishartsock
Path Finder

The lookup simply adds fieldB to events in index=foo where fieldA is matched. If fieldA is not matched, the event still shows up, but fieldB is null. Therefore the not isnull fulfills the "show only results matching fieldA in foo2" requirement.

0 Karma

mgrosholz
Path Finder

Oh, and thanks btw.

0 Karma

chrishartsock
Path Finder

Is fieldA the same name in foo and foo2?

0 Karma

chrishartsock
Path Finder

Not necessarily. But since it is different you will need to rename fieldA to what it is in foo:

index=foo
| lookup foo2 fieldA AS fieldA_name_in_foo OUTPUT fieldB

0 Karma

mgrosholz
Path Finder

I had a typo on my end. It works.

0 Karma

mgrosholz
Path Finder

Sweet we are getting somewhere! I got the output of fieldB but results are still showing all results of fieldA not just what populates compared to the lookup table. <--does that make sense?

0 Karma

mgrosholz
Path Finder

No. It is not. Should it be?

0 Karma
Get Updates on the Splunk Community!

Shape the Future of Splunk: Join the Product Research Lab!

Join the Splunk Product Research Lab and connect with us in the Slack channel #product-research-lab to get ...

Auto-Injector for Everything Else: Making OpenTelemetry Truly Universal

You might have seen Splunk’s recent announcement about donating the OpenTelemetry Injector to the ...

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...