I am sure it would be possible for the team to add some facilities such that you either store less information or perhaps allowing some granularity to be wiped after a certain period of time. I guess you could say that logs are a little like insurance policies in that you hope that you do not need them but …. It keeps quite a detailed amount of information in a fairly compact way because the big problem with logging is that the user does not necessarily know what they need until something happens and even then they may need completely different information than they did on a previous occasion. Glasswire tries to be as flexible as possible in what it does and the way it does things. It’s mainly the firewall functionality that I’m using, and I find that once you actually have a list of hundreds of applications, it starts to become unmanageable for that purpose with no search/sort options or automatic block/ignore/allow rules. Maybe GlassWire just isn’t the program for me? I only really need a generalized look at how much bandwidth an application has used each day this week, then four weekly averages and monthly averages after that, not being able to see every single connection an application has made to the minute from months ago. I don’t know what the solution is, but I find that I don’t need the highly specific information that GlassWire is logging all the time. I suspect that applications which are making lots of small connections are causing this. I’ve also had problems with GlassWire’s log files ballooning in size - often to tens of GB and having to manually clear them every month or so. Many miscellaneous bug fixes and stability 1528×199 12.6 KB.Fixed a bug where publishers would not update correctly when 'traffic' is changed in GlassWire's user interface.

Improved notifications about new 'Things' that joined the network so it has more useful information.

Added more contrast to blue colors in the user interface so the text is easier to read.

Fixed a bug that caused artifacts to appear on the GlassWire main graph.

Fixed a bug that could cause some people to be unable to create firewall profiles.

Fixed a bug that could cause the GlassWire Windows Service to crash.

Fixed a bug that could cause GlassWire to crash when the mini viewer is moved between multiple monitors.

The GeoIP database we use for hosts is now updated.

GlassWire now has a loader animation when the firewall is switched on/off.

GlassWire now has a new notice in 'Block All' mode that some Windows Security features may have network access to avoid virus false positives.

You can also see old devices that are now offline and scanning is much faster! Also, mouse over a device name and click the three dot menu (.) on the right side to add custom information for devices. Click the top right 'settings' icon to use the new different 'Things' options.

Major 'Things' improvements including a completely redesigned user interface.

Fixed an issue that causes all apps to be blocked on the firewall if 'ask to connect' is enabled, and if the GlassWire database is moved from one PC to another.Fixed a crash that could be caused by VirusTotal scanning when an app is on a network share.Fixed a bug that could cause an app started on a network share to be unblockable.Fixed a crash (reported in our forum) that could be caused by running an app from a network storage device.Fixed a bug where the mini viewer had an alert bubble that could overlap its header.Fixed a bug where a graph pop-up could show zero stats in some situations.Fixed a bug that could cause some remote access addresses to not be saved in GlassWire's settings.This option is now on by default for everyone. Removed an option to not show the ports on the firewall tab.Added a warning for our firewall 'block all' mode, so a user who is using our remote monitoring feature will know they are about to block their own connection.You can now see services and process IDs related to your apps on GlassWire's Firewall.

Glasswire forum