Splunk Search

TIME_FORMAT vs DATETIME_CONFIG = CURRENT

vbumgarner
Contributor

I have a log file that has a date at the top, but otherwise is essentially unpredictable stdout. It could be written to for minutes or days.

This seems appropriate and acceptable:
SHOULD_LINEMERGE = False
DATETIME_CONFIG = CURRENT

What I'm wondering is if I have a TIME_PREFIX and TIME_FORMAT, will it try those first? The first line is predictable, so I could at least capture that single real date.

Tags (2)
0 Karma

gacerioni
Engager

Hello!

It will ignore all settings based on the text(raw) event. Also, it follows the same rule as if you put "NONE".

0 Karma

hazekamp
Builder

V,

I believe setting DATETIME_CONFIG=CURRENT or DATETIME_CONFIG=NONE will ignore TIME_PREFIX/TIME_FORMAT (you can only use one or the other; not one then the other).

0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...