LoggiFly

This release adds trigger buffering for log matches and container events, plus a more robust search and filtering pipeline under the hood.

Highlights

You can now configure buffer so that, when a keyword matches, LoggiFly waits a configured number of seconds and collects related log lines before sending one aggregated notification. Container events can also be buffered so that repeated occurrences of the same event are counted during the buffer window.

- keyword: error
  buffer:
    seconds: 10
    mode: matching # optional, defaults to 'matching'
    max_lines: 20 # optional

For all details on this feature refer to the updated docs.

Other behavioral changes and fixes

• Matches suppressed by ignore_keywords no longer consume a trigger_on threshold count or start a trigger_cooldown. So log lines that match ignore_keywords will now no longer affect trigger_on or trigger_cooldown.
• Default title wording changed slightly. Default titles now use the same Jinja2 rendering pipeline as custom title templates.
• trigger_cooldown and trigger_on state for container events is now scoped correctly per monitored container.

Documentation

• Added buffer documentation to the config guide.
• Added buffer template fields to the notification customization guide.
• Added buffer examples to the config reference.

Other

• chore(docker): update image to Debian 13 and Python 3.13 (#103)
• chore(deps): bump js-yaml from 4.1.1 to 5.2.0 by @dependabot[bot] in https://github.com/clemcer/LoggiFly/pull/104
• chore(deps): bump apprise from 1.10.0 to 1.11.0 by @dependabot[bot] in https://github.com/clemcer/LoggiFly/pull/101
• chore(deps): bump requests from 2.34.0 to 2.34.2 by @dependabot[bot] in https://github.com/clemcer/LoggiFly/pull/99

Full Changelog: https://github.com/clemcer/LoggiFly/compare/v2.0.1...v2.1.0