Getting Data In

configuring TIME_FORMAT

kerne1
New Member

Hello, our logs have ISO 8601 date format with shorted year (YY instead of YYYY): "12-08-06 04:42:10". It is 6 of August 2012 but Splunk think it is 12 of August 2006.

I've added to props.conf:
TIME_FORMAT = %y-%m-%d %H:%M:%S
but this didn't change anything.

the full config:


[source::/var/log/access*]
#12-08-03 19:48:40 "user1|g" 1.2.3.4 "CONNECT www.example.com:443"
EXTRACT-access = ^(?P<datestamp>[^ ]+) (?P<timestamp>[^ ]+) "(?P<auth_user>[^|])|(?P<profile>[^"])" (?P<src_ip>[^ ]+) "(?P<method>[A-Z]+) (?P<url>[^"]+)"
TIME_FORMAT = %y-%m-%d %H:%M:%S

any idea how to configure?

thanks

Tags (3)
0 Karma

pmocek
Explorer

Your logs are not using ISO 8601. It specifies four-digit years. There is no provision in it for a two-digit year.

0 Karma

hetzere
New Member

I downvoted this post because op stated the exception, and the comment does nothing to answer the question.

0 Karma

blebit
Path Finder

hello, can we push this from Deployment Monitor ???

0 Karma

dmaislin_splunk
Splunk Employee
Splunk Employee

MAX_TIMESTAMP_LOOKAHEAD=20
SHOULD_LINEMERGE=false
TIME_FORMAT=%y-%m-%d %H:%M:%S
TIME_PREFIX=^

0 Karma

kerne1
New Member

sorry for misleading, the html tags come from Markdown and doesn't belong to the config.

this ist the log line:
12-08-03 19:48:40 "user1|g" 1.2.3.4 "CONNECT www.example.com:443"
this is the props.conf (I've removed the EXTRACT expression for clarity):

[source::/var/log/access*]
TIME_FORMAT = %y-%m-%d %H:%M:%S
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 ...