Splunk Search

Splunks date_* fields not in all records

JensT
Communicator

Hi,

Splunk 4.3.6 (UF, HF, Idx and Srh)

Why are the date_* fields not in all records?

Regards,
Jens

Tags (2)
0 Karma

Ayn
Legend

(from @lguinn's answer in http://answers.splunk.com/answers/99451/variance-betweeen-_time-and-date_-fields )

The date_* fields are a direct parsing of the text timestamp in the input stream. These fields do not exist for inputs that do not use text timestamps; for example, none of them will appear in an input that uses Linux epoch time.

In other words, you should not rely on them being there.

Ayn
Legend

I totally agree. 🙂

0 Karma

JensT
Communicator

Hi,

thanks for the speedy answer. So i consider this as a design flaw.
We have billions of records with these fields (Linux, Unix, Solaris) and millions without (Windows Event Logs).

Its confusing to users and will be hard to explain this, but at least we know that we cannot rely on them.

Regards and thanks,

Jens

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!

Event Series: The Agentic SOC: Trust Before Autonomy

AI is fundamentally changing security operations, but true progress requires more than just automation—it ...

Free Professional Services for .conf26 Attendees

This year at .conf26, we are doing something a little different. We are bringing the best minds from ...

Defend at Machine Speed: Your Guide to Security Sessions at .conf26

Splunk .conf26   With threats moving at machine speed and attack surfaces expanding across hybrid ...