Splunk Search

Query should return last/latest available data when there is no data for the selected time range

saichandjawari
Explorer

Query should return last/latest available data when there is no data for the selected time range

Labels (1)
Tags (1)
0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Essentially, data is returned from the selected time range, if there is no data, what time range do you want to use?

You could do something like this

 

<your search>
| appendpipe
  [| stats count as _count
   | where _count = 0
   | where isnull(_count)
   | append
     [| search <your index> [| metasearch index=<your index> earliest=0
                             | head 1
                             | rename _time as earliest
                             | fields earliest]
      ]
   ]

 

0 Karma

saichandjawari
Explorer

The query is used in a dashboard panel as a statistical table with single row.  the data is usually  not available on regular intervals. Hence we would like to show the last available data instead of “no results found” when there is no data for the selected default time range that we have set.

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

OK, so have you tried what I suggested?

0 Karma

saichandjawari
Explorer

Thanks for your response.

0 Karma

saichandjawari
Explorer

Yes, but that isn’t working. 

So here is a solution that I came up with — 


Step 1 - first write your results to a lookup file. 

<your query> |outputlookup yourlookup.csv

 

Step 2 - use that lookup in the query as shown below:

 

<your query> |append [|inputlookup yourlookup.csv 

|outputlookup yourlookup.csv override_if_empty = false create_empty = false]

 

the above query writes the results and stores in yourlookup.csv with wider time range. And  we are rewriting the stored results to the same lookupfile. In the last line override and Create_empty commands will make sure it will not give empty results. 
Note: use |dedup in the last if you see any duplicate results.

step 3- Create a saved search with this query and schedule it according to your requirement. 

0 Karma
Get Updates on the Splunk Community!

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 ...

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

🔐 Trust at Every Hop: How mTLS in Splunk Enterprise 10.0 Makes Security Simpler

From Idea to Implementation: Why Splunk Built mTLS into Splunk Enterprise 10.0  mTLS wasn’t just a checkbox ...