Splunk Search

Why time filter value/range is not being passed to the query result?

chongdong
Explorer

Does anyone know why the time range picker here on the right side (set to Yesterday Jan 30) cannot affect my _time data field in the query result? How to link them? 

chongdong_0-1675219422905.png

 

Labels (1)
0 Karma

yuanliu
SplunkTrust
SplunkTrust

That's because you re-evaluated _time in the third line shown in the screenshot to "created_at".

| eval _time = created_at

You data may have collected these events from Jan 30, but the field "created" has different values

0 Karma

chongdong
Explorer

Got it. Thanks for the explanation. So is there a way to modify the time filter to point to my timestamp which is created_at? 

0 Karma

yuanliu
SplunkTrust
SplunkTrust

Yes.  if you don't like your current _time at all, you can change your ingestion to use created_at as _time. (This is perhaps not the correct solution in most cases.)

At search time, you can use calculated field to calculate epoch time from created_at and name it _time.

0 Karma
Get Updates on the Splunk Community!

Observability | How to Think About Instrumentation Overhead (White Paper)

Novice observability practitioners are often overly obsessed with performance. They might approach ...

Cloud Platform | Get Resiliency in the Cloud Event (Register Now!)

IDC Report: Enterprises Gain Higher Efficiency and Resiliency With Migration to Cloud  Today many enterprises ...

The Great Resilience Quest: 10th Leaderboard Update

The tenth leaderboard update (11.23-12.05) for The Great Resilience Quest is out >> As our brave ...