Getting Data In

Why doesn't the time format match my log?

kannu
Communicator

Hi splunkers

I have following log entry in file getting indexed on sourcetype name "ncm"

"01/06/2018 12:00:47 : Started LoadBalancer" 

This is of 1st june 2018 but in splunk this entry has been taken as 6 january 2018 . Before this entry comes in the log two days ago i have already changed the time format in props.conf

[ncm]
TIME_FORMAT = %d-%m-%Y %H:%M:%S

So in that two days data arrived as per my time format but today 1st june data went to 6th january .

Please help.

0 Karma
1 Solution

FrankVl
Ultra Champion

That TIME_FORMAT does not match your log. Your log has / as separator, while your TIME_FORMAT uses -. Which will cause Splunk to revert to auto detection, which indeed can fail on ambiguous dates likes 01/06/2018.

View solution in original post

0 Karma

FrankVl
Ultra Champion

That TIME_FORMAT does not match your log. Your log has / as separator, while your TIME_FORMAT uses -. Which will cause Splunk to revert to auto detection, which indeed can fail on ambiguous dates likes 01/06/2018.

0 Karma

kannu
Communicator

@FrankVl

So below will work ?

[ncm]
TIME_FORMAT = %d/%m/%Y %H:%M:%S

0 Karma

FrankVl
Ultra Champion

Yes, I would expect it would 🙂

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!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...