Vankog

Thanks for considering this. Just some insights: I tinkered around yesterday. First, I tried serving the "docker logs ..." output as TCP and added it ...

Hi, I was setting up a new PC and found that you don't serve a Winget package, yet. May I kindly ask if you could consider providing one? https://lear...

Just wanted to let you know that the program icon was broken, when I started LogView Plus via "Run" button inside the update wizard. Restarting the pr...

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

Thanks I already tried it and works great! Thanks for your work! Some things I have noticed: * The Customization dialog has some visual glitches when ...

Hi, I forgot to mention:  Have you noticed, that Reports don't work on Merge nodes? You can only enable "Show Dashboards", but this won't do anyt...

While writing the topic, I also grew unsure about the title, but I though: let's start small, but give the bigger use case.. :-)

[quote]The next best thing to do is to rewrite your filters to process from parent to child. Ideally, parent filters would work with smaller data sets...

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

BTW: a workaround is to Restore Default Columns. But still weird

I would like to give this issue a thumb-up. The colum-chooser from 6 years ago does not seem to exist anymore. I very often have to re-select the colu...

Hello, after  https://www.logviewplus.com/forum/2294/Scrambled-fields-when-parsing-json-properties-with-n I am now on Beta 3.1.18. But the p...

Hello, I try parsing log files in standard logstash format. i.e. json format.  See https://github.com/liangyanfeng/logstash-logback-encoder/tree/...