Getting Data In

Strange timestamp warning

nonaronald
Explorer

Hi everyone,

I'm importing data from Windows event logs to a Splunk machine in Unix (version 7.0.3).

I have a weird warning when I try to do my timestamp configuration.

My logs timestamp looks like this:

2019-03-10 12:04:44:foo: bar ...

So I follow the official doc and I put:
TIME_FORMAT = %y-%m-%d %H:%M:%S:
but I get some warnings and the event breaking is wrong.

Warning: Could not use strptime to
parse timestamp from"2019-03-10
12:04:44:foo..."

Then when I try:
TIME_FORMAT= %y%-%m%-%d %H%:%M%:%S%:
which is surprisingly not a format anywhere in the docs, everything looks fine.

Can anyone help me understand what's going on?
I'm not sure if I'm following the best practices...

I join some screenshots.
Thank you in advance.

With warning: alt text
Without warning: alt text

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

I don't why the second format works, but it shouldn't. Your first format is almost correct, it just needs to be modified to look for 4-digit years.

TIME_FORMAT = %Y-%m-%d %H:%M:%S
---
If this reply helps you, Karma would be appreciated.

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust

I don't why the second format works, but it shouldn't. Your first format is almost correct, it just needs to be modified to look for 4-digit years.

TIME_FORMAT = %Y-%m-%d %H:%M:%S
---
If this reply helps you, Karma would be appreciated.
0 Karma

nonaronald
Explorer

Thank you richgalloway. It was my mistake %Y-%m-%d %H:%M:%S works well but the other format works well too.
That's why I was confused.

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