You can even open multiple chunks and then merge your logs as needed. It can divide the file into chunks and let you decide which chunk you are interested in.

But LogViewPlus can also do something a bit smarter. Opening larger files is constrained only by the amount of memory you have on your machine. LogViewPlus loves large log files and can open a MB log file in about 30 seconds depending on your hardware. This is similar to how tail and grep work, but completely redesigned for Windows. Filters can also be applied automatically while tailing the log file. For example, you can narrow your log file down to a particular thread and then search just within that thread. Filtering your log files is better than searching because filters can be chained. Merging log files can give you greater insight into how multiple processes are interacting with each other. Merged log file entries are automatically sorted by date so the information appears to be written by a single process. I'm sure one day LogFusion wil be the great product we expect, but for now we need to move on.With LogViewPlus, you can open as many log files as you need and press a button to combine them. As it stands, it's completely unclear what BinaryFortress intends with LogFusion or what it will pick up next and what is in the pipeline to be picked up. Even a simple issue tracker would be a big improvement. It would be great if you had a roadmap, a long-term vision, it would be great if you worked with a public Jira back-log or a Trello board. LogFusion's development team communicates suboptimally there's no roadmap, no indication of planned features, no transparent priorities.LogExpert also locks up for some time, but loads the logs in parallel so becomes responsive much faster. Taking a look at Baretail, it opens all logs simultaneously and even when a log isn't loaded the GUI doesn't lock up and you can select the correct tab right away. LogFusion seems to opens logs sequentially and synchronously and is unresponsive while it does so opening LogFusion to get to the right tab is painfully slow.If it did open as a new instance, we could manage our groups that way. It reuses the open window and adds the tabs to it. As far as I know, we cannot start LogFusion from the CLI with a list of logs, to create a new tabbed window.Then getting the cleared lines back means we need to close and reopen the log manually, which also displaces the tab to the end. For example, to reduce noise just before a test, we will clear the log (which is only a visual change, the actual log remains unchanged). When right-clicking on a log and selecting Clear Log (not deleting it!), then the screen is cleared, but there is no way to reload the file to get the logging back.For example we are logging serialized JSON or fixed-width messages, but LogFusion is showing an ellipsis instead (even after double clicking the capped line).

Long lines being logged are not shown entirely.

Much more coming up (yes we have an Elastic Stack, no it cannot replace hands-on log viewers). This is just three development teams managing one process. In our enterprise environment, we can have 88 logs in total, 26 for our test and acceptance servers each, 36 more for production servers. Either by tab-grouping or by multiple viewer instances each with their own group of tabs or even have colored tabs to keep it grouped manually (although cycling tabs really becomes a pain).

This one should be obvious by now, but we need some way to group our log files.

We had high hopes for LogFusion, but there are a couple of issues that prevent us from loving it. We are not rolling out LogFusion to our entire user base and have started shifting to a different vendor for viewing logs, but I wanted you know why.

Baretail pro multiple logs