Splunk Search

Last vs Max in Timestamp

lucas4394
Path Finder

I wonder what the difference between last and max in timestamp if I want to return the most recent time from a lookup. Both of them return the same result as showed below. Any comments?

| makeresults 
| eval last_seen=strptime("05/06/2019 5:43:32","%m/%d/%Y %H:%M:%S") 
| append 
    [| makeresults 
    | eval last_seen=strptime("05/06/2019 16:12:00","%m/%d/%Y %H:%M:%S")] 
| stats max(last_seen) as max_last_seen last(last_seen) as first_last_seen 
| eval max_last_seen=strftime(max_last_seen, "%m/%d/%Y %H:%M:%S"), first_last_seen=strftime(first_last_seen, "%m/%d/%Y %H:%M:%S")
Tags (1)
0 Karma
1 Solution

woodcock
Esteemed Legend

Using max(_time) is far more efficient than using latest(_time) because it does less work. One should ALWAYS use max(_time) over latest(_time).

View solution in original post

woodcock
Esteemed Legend

Using max(_time) is far more efficient than using latest(_time) because it does less work. One should ALWAYS use max(_time) over latest(_time).

woodcock
Esteemed Legend

Furthermore, if you are POSITIVE that you results will ALWAYS be sorted (keep in mind that in low-RAM situations, sometimes events are not returned fully sorted), you can use first(_time) which is the fastest and most-efficient of them all.

0 Karma
Get Updates on the Splunk Community!

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...