Splunk Search

Use variable as complete search string

ameyad
Engager

I am trying to create a dashboard. It has two input text fields.
I want to run a search query based on these two inputs.

If input A is null AND input B is null then no search results
If input A is not null AND input B is null then search using only A
If input A is null AND input B is not null then search using only B

If input A is null AND input B is not null then search using both A and B

Following is my query. It returns no results 

 

Properties.application="xyz.api"
| spath Level 
| search Level!=Verbose AND Level!=Debug
| eval search_condition_fnum=if(len(trim("$text_fnum$"))=0 OR isnull("$text_fnum$"), "", "RenderedMessage=\"*$text_fnum$*\"")
| eval search_condition_fdate=if(len(trim("$text_fdate$"))=0 OR isnull("$text_fdate$"), "", "RenderedMessage=\"*$text_fdate$*\"")
| eval combined_search_condition=mvjoin(mvfilter(search_condition_fnum!="") + mvfilter(search_condition_fdate!=""), " OR ")
| table search_condition_fnum, search_condition_fdate, combined_search_condition
| search [| makeresults | eval search_condition=mvjoin(mvfilter(search_condition_fnum!="") + mvfilter(search_condition_fdate!=""), " OR ") | fields search_condition]

 



Labels (2)

yuanliu
SplunkTrust
SplunkTrust

It appears to me that you are overthinking the search language.  Assuming that RenderedMessage is already extracted (as is implied in your illustrated code), you can use

roperties.application="xyz.api"
  (RenderedMessage="*$text_fnum$*" AND RenderedMessage="*$text_fdate$*")
| spath Level 
| search Level!=Verbose AND Level!=Debug
| eval combined_search_condition=mvjoin(mvfilter(search_condition_fnum!="") + mvfilter(search_condition_fdate!=""), " OR ")

If you run this on paper, you will see that the wildcards will cause the search to behave as you described.

Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...