Here's an example beginning of an event line
Oct 20 20:57:03 sfo-prd-wsux02 apache2: [Fri Oct 20 20:57:03.398765 2017] [proxy:error] [pid 32083:tid 140031679186688]
I'm trying to capture the second timestamp as "Fri Oct 20 20:57:03.398765 2017" that includes the subseconds
In props.conf I am putting:
TIME_PREFIX = ^.*[
TIME_FORMAT = %a %b %d %H:%M:%S:.%6N %Y
However Splunk's timestamp is catching the decimals, please advise.
Thank you all
@vlicoupons - if your issue has been solved, then please accept the answer so the question will show as closed. Also, please feel free to upvote any comments or other answers you found useful. If you still have open issues regarding this, please let us know how else we can help.
TIME_PREFIX is also doing a greedy match, so it may be passing over the field you want, deciding it doesn't have a valid timestamp, and then defaulting to the first timestamp it sees. Use a lazy match like this:
That will stop at the first square bracket instead of the last one.