Splunk Search

Stringing together searches

ecnausysadm
Explorer

I have searches for two files that are related but the incoming and outgoing file names differ, basically it's an incoming order from a buyer and then the outgoing message to the supplier;
incoming_filename | transaction source host
outgoing_filename | transaction source host

Both of these give the required search results when run separately.
Now I want to be able to put both searches in and display the results, basically join the search for the incoming and outgoing files so I can see when they came in and went out in their separate logs.

I can get APPEND to partially work so I think that might be the right path, eg this returns the results for incoming_filename but it doesn't show anything for the outgoing_filename search after the APPEND;
incoming_filename | transaction source host APPEND [search outgoing_filename | transaction source host]

This might be obvious, but I haven't found a way as I'm new to Splunk and not sure if I am on the right track or should be using some other operator (I also tried OR and JOIN with no luck).

Cheers,
Mark

Tags (2)
0 Karma
1 Solution

Ayn
Legend

It sounds like you should be able to accomplish what you want simply by having an initial OR clause in your search:

incoming_filename OR outgoing_filename | transaction source host

You mentioned that you've tried OR without success - can you elaborate on what you tried and why it didn't work?

View solution in original post

Ayn
Legend

It sounds like you should be able to accomplish what you want simply by having an initial OR clause in your search:

incoming_filename OR outgoing_filename | transaction source host

You mentioned that you've tried OR without success - can you elaborate on what you tried and why it didn't work?

ecnausysadm
Explorer

Yep that was it!
I thought I had to run search1 and then search2 and join them, I didn't even think of doing the OR based on the unique search string (ie the filename). In hindsight that's pretty obvious.

I had tried;
PO_15485669.135 | transaction source host OR PO20120526_6839471.EDI | transaction source host

Thanks for that.

0 Karma
Get Updates on the Splunk Community!

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...

Tech Talk | Elevating Digital Service Excellence: The Synergy of Splunk RUM & APM

Elevating Digital Service Excellence: The Synergy of Real User Monitoring and Application Performance ...