Getting Data In

Props not considering AM PM

ahmadshakir1952
Explorer

Splunk Props is not considering AM PM. Need to consider AM PM value and convert the time into 24 hour time format for the below sample log.

Log Sample:

5465465||TEXT||546546545445|65465|TEXT|TEXT|TEXT|TEXT|||0||TEXT||TEXT||||||||TEXT||13-JAN-20 06.09.59.000000 PM|||||||||||||||

Existing Props configuration:

DATETIME_CONFIG =
FIELD_DELIMITER = |
INDEXED_EXTRACTIONS = csv
KV_MODE = none
NO_BINARY_CHECK = true
SHOULD_LINEMERGE = false
TIMESTAMP_FIELDS = "Field name where time is exist with am/pm"
category = Structured
disabled = false
pulldown_type = true

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Try telling Splunk what the timestamp field looks like.

TIME_FORMAT = %d-%b-%y %I.%M.%S.%6N %p
---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Try telling Splunk what the timestamp field looks like.

TIME_FORMAT = %d-%b-%y %I.%M.%S.%6N %p
---
If this reply helps you, Karma would be appreciated.
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 ...