Posted on Feb 18, 2020 at 6:56 AM
Hi Colin,
Thanks for bringing this issue to my attention.
That is a very tricky date to parse. In particular, LogViewPlus is going to struggle with having the timezone twice as this is not supported by our underlying technology (.Net). The placement of the time zones is also preventing us from parsing the year. Because we don't have access to the year, it is confusing to parse Wed Oct 31. Not every Oct 31st is also a Wednesday.
Normally, I would recommend applying a time offset after parse, but this feature is not built to offset years. I will revisit this to allow for more coarse changes.
The only solution I can think of at the moment is to write a custom parser or scrub the data. Please see:
https://www.logviewplus.com/docs/custom_parsers.htmlhttps://www.logviewplus.com/docs/open_commands.htmlIf you could convert " GMT+10:00" to "+10:00", then the date could be parsed with: ddd MMM dd HH:mm:sszzzz yyyy
There is another issue here. All dates must have a year and if a year is not provided the current year is assumed. This is why the format %d{MMM dd %H:mm:ss} resolves to the year 2020. Oct 2020 doesn't make sense for a log file in Feb 2020. A better assumption would be Oct 2019. I will make this change for the next release. However, since your year is actually 2018, it will not be much benefit here.
Hope that helps,
Toby