This document describes CLS LogListener versions.
- Multi-line - full regular expression collection mode is available starting from LogListener v2.4.5.
- Automatic LogListener upgrade is available starting from LogListener v2.5.0.
- Uploading logs of parsing failures is available starting from LogListener v2.5.2.
- You are advised to install or upgrade to the latest version for a better user experience.
|v2.5.3||Bug fix||Fixed LogListener exceptions caused by memory issues.|
|v2.5.2||New feature||Added support for uploading logs of parsing failures.|
|Bug fix||Fixed a blocklist bug. Now the blocklist FILE mode supports wildcard filtering.|
|v2.5.1||Experience optimization||Enhanced the handling when breakpoint metadata could not be found in the collection file.|
|v2.4.5||New feature||Added support for `multiline_fullregex_log` log collection.|
|v2.4.4||Bug fix||Fixed the issue of inaccurate log time caused by the msec feature.|
|v2.4.3||New feature||Added support for automatically checking the log format (logFormat).|
|v2.4.2||Bug fix||Fixed the issue of cache eviction of related configurations when pulling configurations under Tencent Cloud container scenarios.|
|v2.4.1||New feature||Added support for collecting logs in milliseconds.|
|Bug fix||Fixed exceptions due to no line break data in user logs.|
|v2.4.0||New feature||Added support for instance-level process monitoring.|
|v2.3.9||New feature||Added support for blocklisting collection paths.|
|Bug fix||Fixed the memory leak issue due to outdated Boost library.|
|v2.3.8||New feature||Added support for multi-path log collection.|
|v2.3.5||New feature||Added support for log context search.|
|v2.2.6||New feature||Added support for configuring private domain and public domain separately.|
|Bug fix||Fixed LogListener exceptions caused by `getip` .|
|v2.2.5||New feature||Added support for Tencent Cloud COC environment deployment.|
|Bug fix||Fixed the issue of core loss or corruption caused by `getip` .|
|v2.2.3||Experience optimization||Renaming or creating logs during log rotation will not cause log loss.|
|v2.2.2||Experience optimization||A log greater than 512 KB will be automatically truncated.|