clientIP and date in logs, but in Date seconds are ignored.

[vijayakumarkb]

I have a strange issue, not sure if this could be the reason.

In my logs. Client IP and Date is logged, but in splunk in Time Column, the date is displayed with seconds as zero
Eg : log as below
ClientIP="10.111.222.333" acceptHeader="application/json; charset=UTF-8" dateTime="[15/Jan/2020:05:02:08 +0000]"
so in Date column it is shown as 1/15/20 5:02:00.000 AM instead of 1/15/20 5:02:08.000 AM
This happens only when the clientIP value contains 3 numbers in the last field. ie this ip last field is 333 so when we have 3 numbers in the last field, splunk is ignoring the seconds in Date column.

Correctly displaying

Eg : log as below
ClientIP="10.111.222.44" acceptHeader="application/json; charset=UTF-8" dateTime="[15/Jan/2020:07:06:05 +0000]"
so in Date column it is shown as 1/15/20 7:06:05.000 AM, so clientIP last value is 44, only 2 numbers, so it is displaying correctly.

Anyone have any idea? Any help appreciated.

[vijayakumarkb]

Thanks a lot team, it worked. Happy 🙂

[richgalloway · Accepted solution]

The props. conf settings are inadequate. @marycordova is on the mark. Try these settings.

[access_log]
SHOULD_LINEMERGE = false
TIME_PREFIX = \[
TIME_FORMAT = %d/%b/%Y:%H:%M:%S %Z
MAX_TIMESTAMP_LOOKAHEAD = 26

[richgalloway]

What are the props.conf settings for that sourcetype?

[marycordova]

suspect the max timestamp lookahead is set to too low of a value so when the IP address has more characters the timestamp runs beyond the lookahead limit

the props config and a sample of the raw data with both a short and a long ip could confirm

[vijayakumarkb]

[access_log]
SHOULD_LINEMERGE = false

This is the only entry in props.conf

[vijayakumarkb]

sample of data

ClientIP="10.111.222.333" acceptHeader="application/json; charset=UTF-8" dateTime="[15/Jan/2020:05:02:08 +0000]"