OK, it seems the wording confused me.
When I target "Log File", it actually creates the filter on the merge node, not the real log file.

It turns out, the "Find in Log FIle" command also selects the merge node. Did this change recently? I thought in the past it really switched to the referenced log file instead.

So, this topic seems to be resolved already.

What I found, though, is that the created filter is not case-sensitive, even though I enabled it by default.
Could you let the Instant Text Filter feature follow this setting?
Thanks!

In my workflow I always merge multiple log files, because we have multiple server instances and multiple types of logs.
So it only makes sense to analyse issues with all logs combined.

Often I like to drill down to affected session IDs to analyse the flow of events.
Usually, I do this manually via SQL scratchpad (see https://www.logviewplus.com/forum/2325/Save-SQL-prompts for that) and setting up a text filter on the top level.

I realized that there is an Instant Text Filter option in the context menu.
However, for some reason, it is not possible to target the merge node directly:

(see attached instant filter target.png)

Thus, this feature is basically useless to me, as you can probably see.

In general I'd really appreciate it if the merge node would become more of a first-class citizen in LogViewPlus. Several features are not working well with it, even though it is THE main feature of LogViewPlus for me.

Thanks for considering this!
Best regards,
Danie