Release 25.2.0

Introduces search term occurrence counts and fully customizable, reusable Search Term Groups for flexible log filtering.

Featured image for Release 25.2.0

Release 25.2.0 introduces two significant improvements to how search terms work: hit counts per term, and fully reusable Search Term Groups.

This release also moves LogoRRR to the Java 25 and JavaFX 25 runtime generation and refreshes the build pipeline for Maven 4.

Occurrence counts per search term

Search term panel showing match counts per term
Each search term now displays the number of matching log lines — at a glance you can see which terms are firing and how often

The search term panel now shows how many times each term matches the current log file. This surfaces patterns quickly: if SEVERE has 3 hits and WARNING has 400, the ratio alone tells a story before you read a single line.

Search Term Groups

Search Term Groups selector in the toolbar
The toolbar selector lets you switch between saved Search Term Groups, while the edit button opens group management

A Search Term Group is a named set of search terms that can be saved and reloaded. This replaces the need to re-enter the same filters every time you open a file from the same source.

  • Save and reuse: Name a configuration and switch to it with one click.
  • Global or file-specific: Mark a group with ❤️ to make it available for every log file; leave it unmarked to keep it tied to the current file.
  • Built-in defaults: Two groups ship out of the box — default (FINEST / INFO / WARNING / SEVERE) and empty (clears all terms).
  • Automatic selection: When you open a file, LogoRRR applies the last group you used. For a new file, it falls back to default.

Groups are managed through the new Settings menu item.

Live monitoring and packaging

The tailing implementation was reworked so LogoRRR can follow growing log files more reliably. Linux packaging was expanded with amd64 and arm64 GraalVM builds, improved .deb naming, and a cleaner Flatpak build structure.