Need help on time prefix

[hikari992]

Hi everyone, i have an xml data have this created date that look like this:

<...> 2013-05-16T06:03:13.103 <...>

This is my props.conf file:

[mysourcetype] BREAK_ONLY_BEFORE = NO_BINARY_CHECK = 1 SHOULD_LINEMERGE = true TIME_PREFIX=

So, the problem is at the search result page it doesn't display the timestamp that I wanted. Did i set the time prefix correctly?

Any help is appreciated.
Thanks

[kristian_kolb]

What time does splunk extract from the example above? Something wildly different?

There will be two fields called starttimepos and endtimepos that gives the boundaries/offset from where in an event that Splunk identified the timestamp. Make sure that you've hit the right timestamp.

If you can post a full event, it would be helpful, and also add information on the time Splunk thinks is right, and the values of starttimepos and endtimepos for that event.

Also, you might need to tune MAX_TIMESTAMP_LOOKAHEAD and TIME_FORMAT (although this time format should be recognized without problem).

/K

[kristian_kolb]

Post a full event. Mask any sensitive data as needed - but please post a full event.

Highlight the timestamp you want/need splunk to understand.

Obviously it does not parse the time properly. There will most likely be DateParserVerbose error messages in the splunkd.log file. Don't know if they will tell you why it didn't work to parse your timestamp, though.

[hikari992]

Hi, thanks for responding. Splunk did not extract the time I've set, the time it display is the time that the xml data stream in.

The actual data is as such:



[contents]

But when included this in my props.conf
TIME_PREFIX=

It shorten data to:

without the "" part of the data, which is the data that i will be needing to use for my work. Does the line breaking entry cause this to happen?

This is my line breaking part of the props.conf
BREAK_ONLY_BEFORE =

[kml_uvce]

use MAX_TIMESTAMP_LOOKAHEAD= also in stanza.
try integer=23

-Kamal Bisht

[hikari992]

Hi, thanks for responding. Sorry, it doesn't work.