Skip to content

v2.1.1

Latest

Choose a tag to compare

@clemcer clemcer released this 15 Jul 06:56
86302c3

Highlights

Configure buffer and trigger_on config via docker labels

The new buffer feature introduced in v2.1.0 as well as trigger_on are now available in docker label configurations.

loggifly.keywords.0.buffer.seconds: 5
loggifly.keywords.0.buffer.mode: "all"
loggifly.keywords.0.buffer.max_lines: 10
loggifly.keywords.1.regex: 'download.*failed' 
loggifly.keywords.1.trigger_on.count: 5
loggifly.keywords.1.trigger_on.timeframe: 60

buffer via environment variables

Configure global buffer settings via environment variables (translates to global.defaults.buffer

environment:
  BUFFER_SECONDS: 
  BUFFER_MODE: all
  BUFFER_MAX_LINES: 10

Configurable connection-pool size for TCP-based connections and a higher default

When connecting to Docker over HTTP or HTTPS, commonly through a socket proxy, LoggiFly could emit warnings such as:

WARNING - Connection pool is full, discarding connection: <host>. Connection pool size: 10

This was caused by the default connection-pool size of the HTTP adapter used by the Docker SDK and only applied to TCP-based HTTP/HTTPS connections.
The warning did not affect LoggiFly's functionality. The pool size controls how many completed TCP connections can be retained for reuse and does not limit the number of concurrent connections.
Nevertheless the warning was noisy and a default of 10 did not properly reflect the typical workload of LoggiFly, monitoring often times dozen of containers.
LoggiFly now uses a default pool size of 64 and you can override it with the DOCKER_POOL_MAXSIZE environment variable.

Normalized boolean values

Writing 'true ' (with a whitespace) no longer causes an error in the config.

Full changelog

  • feat: support buffer and trigger_on config via docker labels
  • feat: env vars for buffer config
  • fix: normalize boolean values and always warn on ignored config fields for docker labels
  • feat: make Docker TCP connection pool size configurable
  • fix: warn on all unsupported docker labels
  • docs: document buffer config via env and docker labels
  • refactor: improve logging and act on 'die' event in event handler instead of 'stop'
  • docs: document trigger_on config via docker labels
  • chore(deps): bump docker from 7.1.0 to 7.2.0 by @dependabot[bot] in #110
  • chore(deps): bump apprise from 1.11.0 to 1.12.0 by @dependabot[bot] in #108

Full Changelog: v2.1.0...v2.1.1