Getting Data In

Time Format being ignored, why?

tyronetv
Communicator

Sample log line date part:

Nov 16 22:48:36

props.conf on indexer


TIME_PREFIX = ^
TIME_FORMAT = %b %e %H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD = 15

Time reported in Splunk - 11/17/13 12:48:36.000 AM

I use "%e" because the day field is populated without leading zero's.

What am I doing wrong?

Tags (2)
0 Karma
1 Solution

tyronetv
Communicator

1) Splunk is showing me the 'offset' time based upon my TZ setting.
2) For some reason, for this source type ONLY, splunk is showing the AM/PM declaration. Not sure why.

View solution in original post

0 Karma

tyronetv
Communicator

1) Splunk is showing me the 'offset' time based upon my TZ setting.
2) For some reason, for this source type ONLY, splunk is showing the AM/PM declaration. Not sure why.

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