Splunk Search

filter inputlookup table by UI specified timerange

BradL
Path Finder

I've been searching and experimenting for quite a while and I suspect I'm missing something simple....

I have a CSV lookup file with an epoch time field ("timestamp").

In my search string, I use inputlookup and I want to filter it, like this:

...| inputlookup my.csv | where timestamp >= start AND timestamp <= end

but the values I want to use for "start" and "end" I want to be the values that come from the UI in the search App (Last 24 hours, etc.)

I would expect these to translate to some sort of pre-defined variables, but I haven't been able to track them down.

I've also tried:

| inputlookup my.csv | eval _time=timestamp

where I hoped the predefined range would apply, but it didn't filter the lookup at all.

Is there a way I can get the UI generated search range to use in my where clause?

Thanks!

Tags (2)
1 Solution

somesoni2
Revered Legend

Give this a try

| inputlookup my.csv | where timestamp >= [| gentimes start=-1 | addinfo | eval search=info_min_time | table search] AND timestamp <=[| gentimes start=-1 | addinfo | eval search=info_max_time | table search]

View solution in original post

somesoni2
Revered Legend

Give this a try

| inputlookup my.csv | where timestamp >= [| gentimes start=-1 | addinfo | eval search=info_min_time | table search] AND timestamp <=[| gentimes start=-1 | addinfo | eval search=info_max_time | table search]
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...