Splunk Search

_time improper format

kannu
Communicator

Hello splunkers,

I have logs in my file
01-03-2018 15:54:58 WARNING [PID:88888][TradeId:11551427] /apps/abcrc/src/check/src/mx_rtpr.cpp:1146 - Sanity Check Exception void sanity_check(void*, rtPRICING_API_LIBRARY*)@/apps/abcrc/Flex/src/mx_rtpr.cpp:1034:End date not equal to option expiry date

that log is of 1st march 2018 but splunk has taken it as a log of 3 January 2018 , please suggest how to manipulate _time field so that my new data or existing data will come in proper time format .

0 Karma
1 Solution

493669
Super Champion

Include TIME_FORMAT in props.conf

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

View solution in original post

493669
Super Champion

Include TIME_FORMAT in props.conf

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

skoelpin
SplunkTrust
SplunkTrust

It would also be good to specify TIME_PREFIXand MAX_TIMESTAMP_LOOKAHEAD so splunk knows where the timestamp is located

[sourcetype_name]
TIME_PREFIX = ^
TIME_FORMAT = %d-%m-%Y %H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD = 20
Get Updates on the Splunk Community!

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...

Purpose in Action: How Splunk Is Helping Power an Inclusive Future for All

At Cisco, purpose isn’t a tagline—it’s a commitment. Cisco’s FY25 Purpose Report outlines how the company is ...

[Upcoming Webinar] Demo Day: Transforming IT Operations with Splunk

Join us for a live Demo Day at the Cisco Store on January 21st 10:00am - 11:00am PST In the fast-paced world ...