Hi Marc,
Thanks for the detailed issue report.
I think you might be coming at this from the wrong angle. LogViewPlus really wants all log entries to be in the same format, so it has one schema definition for the log file. We do support a multi-parse scenario, but this should not be used for log message parsing.
Instead, I would suggest you use a simplified parser for the log file:
%d{dd.MM.yyyy %H:mm:ss:fff} [%t] %c %method %p: %m%nThis will load your log file and ignore differences between log messages. Once loaded, you can parse the log entry messages separately:
I would suggest using a
Regex Parser for this task:
\(duration=(?<duration>\d+(\.\d+)?)(?=[,\)])
This will create a parse message filter which isolates the duration values:
From there, it should be straight-forward to apply your SQL statement:
Regarding the screenshots provided above:
- The first is likely failing because with your original parsing strategy, some of your Duration column values are null. Hence - "no data found".
- The second statement is simply saying "your SQL statement is valid". LogViewPlus only attempts to execute statements once the "Apply" command is executed.
- It looks like the third issue is a variation on the first. You have null values for some of your "Rows" columns. So - "no data found".
Hope that helps,
Toby