I have filtered down some error messages in my Merge node. like

[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."
} 

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".

"error":\ "(?<ProdType>\w+)\ No\.\ (?<SKU>\w+)\ is\ not\ assigned\ to\ any\ catalog\."

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?