LogViewPlus Support » LogViewPlus Support » Help & Support » Parsing a tab seperated log file

Parsing a tab seperated log file

Maarten Mostert — Thu, 20 Jan 2022 15:05:49 GMT

Hello,
I have a tab-separated log file for which I don't manage to define a correct DSV parser.
Some entries are given below

----
2022-01-20 09:25:22.561    #removed    Smalltalk.UI.MenuView        menuWindowOn:in:    Smalltalk.UI.TransientWindow    class    aPostedMenuIn:
2022-01-20 09:25:22.579    #removed    Smalltalk.UI.MenuView        mapAndStartup:    Smalltalk.UI.MenuController        startUp
2022-01-20 09:25:23.707    #removed    Smalltalk.UI.MenuView        highlightedMenuItemView:    Smalltalk.UI.MenuItemView        resignSelection
2022-01-20 09:25:23.710    #changed    Smalltalk.UI.MenuView        highlightedMenuItemView:    Smalltalk.UI.Controller        sensor
-----
Thanks for any help.
Maarten,

RE: Parsing a tab seperated log file

LogViewPlus Support — Thu, 20 Jan 2022 15:05:49 GMT

Glad to hear that is working for you Maarten. Please don't hesitate to get in touch if something is not clear.

Thanks,

Toby

RE: Parsing a tab seperated log file

Maarten Mostert — Thu, 20 Jan 2022 14:49:50 GMT

Many thank syou this works 👍
I had been struggling with documentation for a few hours without getting there 🤷‍♂️
Cheers,
Maarten,

RE: Parsing a tab seperated log file

LogViewPlus Support — Thu, 20 Jan 2022 10:00:00 GMT

Hi Maarten,

This should be pretty straight-forward for LogViewPlus. I am not sure the version of the log entries pasted above matches the tab situation you are seeing locally. I assume that all of the whitespace in these log entries represents a single tab. If this is the case, I am able to get a pretty good parse with:
[code]%d{yyyy-MM-dd %H:mm:ss.fff}\t%S{Status}\t%S{Class1}\t%S{Class2}\t%S{Class3}\t%S{Class4}\t%m%n[/code]

I am using \t here to represent tabs. LogViewPlus understands this notation - which might help you make things more clear. Tabs are also supported, so it is up to you.

The only other gotcha I can see is that the number of columns appears to be variable. It looks like the first row contains an extra column with "aPostedMenuIn:". All log entries must follow the same format, so a fixed number of columns is needed. It is best to use %m to capture columns over the fixed size. In this scenario %m is used to capture "the rest of the log entry".

Hope that helps,

Toby