LogViewPlus Support » LogViewPlus Support » Help & Support » Problems with Message Parsers on Merge nodes

RE: Problems with Message Parsers on Merge nodes

Vankog — Fri, 11 Apr 2025 08:13:37 GMT

Thanks for your work.

What I found is that matching by normal pattern and regex seem to be more reliable now. So I guess, this was fixed? Nice one.
Editing a parser is now also possible on the filter entry. (However, it is still not possible to do so in settings.)

Some of my other issues still apply.
[quote]

I also could not find a way to re-use them properly, even on other logs of the same parser.

EDIT: I can only create new ones, but I cannot apply existing one.

Also, if I go the a Merge node afterwards, I can only re-create ~~the Message Parser that was created last.~~ an old Regex message parser.

EDIT: This one did change slightly. Now the dialog is always prefilled with an old Regex parser and no matter what I tried, this did not change. I tried deleting existing parser, adding new ones etc. - It still only allows me to create that particular parser config.

very minor: I just wondered, why do the spaces get escaped by default in regex mode?

[/quote]

Hope this helps!
Thanks!

Problems with Message Parsers on Merge nodes

Vankog — Fri, 11 Apr 2025 08:07:41 GMT

I have filtered down some error messages in my Merge node. like
[code][2025-01-10 12:51:31.800 +0000] INFO ish13-foo-lv-app000001.internal.cloudapp.net ES1 appserver0 [FOO-TDE-Site] [-] com.foo.intershop.esb.internal.service.FooESBServiceAdapter [] [Storefront] [CU5y42oenlRP5A2fH3AW4GsUs-ZdttC2Jhu9qLRAs-Zdtg==] [_GlbAGeBF9JlAwEK-0-00] "_GlbAGeBF9JlAwEK-0-00" (requestID: e5e420566d444e7f9c8e5004599102f6) Response [Execution time in ms: 68]
{
"error": "PunchingTool No. 000000000002602397 is not assigned to any catalog."
} [/code]
I want to extract some data from it.

Unfortunately, I cannot properly create a Message Parser from a Merge node, so I skip to the log file itself and add a Parser with a Regex pattern with precondition to contain "is not assigned to any catalog". [code]"error":\ "(?<ProdType>\w+)\ No\.\ (?<SKU>\w+)\ is\ not\ assigned\ to\ any\ catalog\."[/code]
This works fine on the log file.

I then go back to my filter on the Merge node.
I add Message Parser, which contains the last created one and add it.
This seemingly worked, but it turns out, it ONLY shows the 9 entries from the original log file, instead of the 338 of the Merge node filter.

This is a bummer.
Is there a way to enable Message Parsers on Merge nodes and their nested filters properly?

Further:

I could not get this Parser to work with the normal pattern for some reason, so I had to use regex. No idea what the issue is as the pattern should be straight forward.
I could not find a way to edit existing Message Parsers. I can only delete them from the settings.
I also could not find a way to re-use them properly, even on other logs of the same parser.
Also, if I go the a Merge node afterwards, I can only re-create the Message Parser that was created last.
I just wondered, why do the spaces get escaped by default in regex mode?

Hope this helps to.
Daniel

RE: Problems with Message Parsers on Merge nodes

LogViewPlus Support — Fri, 11 Apr 2025 06:49:02 GMT

Hi Daniel,

I just wanted to let you know that we have now released LogViewPlus v3.1.21 as a BETA release.

This release addresses the issue with parsing message information across multiple lines.

Hope that helps. Please do let me know if you have any further questions or issues.

Toby

RE: Problems with Message Parsers on Merge nodes

LogViewPlus Support — Sun, 26 Jan 2025 19:55:30 GMT

Hi Daniel,

Thanks for reporting this issue.

Looking at the example you provided, I am having some issues as well. I would expect to parse out information in the "error" field of the provided JSON, but this isn't working as expected. I will need to look into it and get back to you.

Thanks again,

Toby