Splunk Search

How to exclude events where the date greater than today?

ebruozys
Path Finder

Hi,

Is there a way to exclude events in a search where a specific date field (not timestamp) is greater than today. Sow i only want to see events where the specified date field is today or smaller.

0 Karma
1 Solution

FrankVl
Ultra Champion

Try the following, which first parses the date field into a proper date/time value. Then calculates the date/time value for today and then filters events that have a date smaller or equal to today.

... your base search ...
| eval filterdate = strptime(date,"%Y-%m-%d")
| eval today = relative_time(now(),"-0d@d")
| where filterdate <= today

View solution in original post

FrankVl
Ultra Champion

Try the following, which first parses the date field into a proper date/time value. Then calculates the date/time value for today and then filters events that have a date smaller or equal to today.

... your base search ...
| eval filterdate = strptime(date,"%Y-%m-%d")
| eval today = relative_time(now(),"-0d@d")
| where filterdate <= today

ebruozys
Path Finder

Hi Frank,

This is the answer I was looking for. I would rather exclude it in the base search but I guess with the readable time format that is not possible.

0 Karma

FrankVl
Ultra Champion

Can you provide some info on what field that date is in and how it is formatted?

0 Karma

ebruozys
Path Finder

The date field is in a human readable format as follows 2018-03-27 00:00:00.0, sow its YYYY-MM-DD.

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