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
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...