Group: Forum Members
Posts: 6,
Visits: 22
|
I agree it's an unusual date format, and I'm not the least bit surprised you've not seen it before, I certainly hadn't. For the moment I may consider pre-processing the logs to turn those values into numbers of microseconds.
For reference, here's a couple of other lines: 1566086399.889997: openAviSegment took 0 ms 1566089999.981911: video buffer full - dropping frame 1566090000.14852: video buffer full - dropping frame 1566090000.47759: video buffer full - dropping frame 1566090000.80712: video buffer full - dropping frame 1566090000.113648: video buffer full - dropping frame Note that as you'd expect for a fractional value, there's sometimes fewer digits after the decimal. I'm not clear whether this particular implementation can end up without the decimal at all (I've never noticed it hit exactly on the second before). I wouldn't be shocked to see the decimal entirely missing (1566086399), a single zero (1566086399.0) or even the entirely stupid just the decimal (1566086399. )
Also, for anyone coming along later, the link for the Pattern Parser docs in the reply above appears to have an extra invisible character at the end. Manually copy and paste it into your browser and delete the junk, and it's fine.
Thank you.
|