Version Number | Change Type | Description | Documentation |
v3.6.0 | Experience optimization | json collection supports uploading raw content. The new architecture optimizes time parsing during collection and supports parsing non-standard time formats. Optimized the issue where old version processes occasionally could not be killed normally during the upgrade to version 2.x. Fixed the issue where collection was blocked when a Job-type task contained an initcontainer, as the pod remained in a non-ready state. | - |
v3.5.15 | Experience optimization | Fixed the scenario where health check logic fails due to send blocking. | - |
v3.5.14 | Experience optimization | Supported service role temporary keys during collector installation. | - |
v3.5.13 | Experience optimization | Optimized the high memory usage issue caused by event queue backlog due to excessive rotation events in rapid rotation scenarios. It supports detecting container events through CRI and polling. Fixed the issue where CPU usage reached 100% in specific scenarios where a line break was missing at the end. Fixed the issue where, in a container scenario with a pod containing two containers, one container remained abnormal, causing the pod to stay in a non-ready state, and logs from the normally started container were not collected. Fixed the issue where, in a container scenario with a pod containing two containers, if both containers mount the same volume or hostpath, it results in duplicate collection. Fixed the issue where, after a pod is destroyed, collection configurations for standard output in the logconfigv2 version persist. This persistence can cause container metadata information to be missing. Fixed the issue where metadata is occasionally missing in TKE environments. | - |
v3.5.12 | Experience optimization | It supports self-healing capabilities. Fixed the issue where, in the moveto scenario, files are cleaned up immediately, causing the reader creation to fail and return null, which in turn leads to a program crash. Fixed the issue where, in docker scenarios, log collection points are cleaned up after a delete event is triggered, resulting in duplicate log collection. | - |
v3.5.11 | Experience optimization | Optimized the upgrade script to disallow upgrading versions below gcc 4.8.5 to the new architecture. kubeclient has been removed from the new architecture eks version of LogListener. Fixed the issue where, after a new collection path is added to the incremental collection configuration, the system did not collect logs from the new path according to the incremental policy, but instead collected historical logs that were written before the configuration was modified. Fixed the issue where, when multi-line full-text logs are collected from container standard output, the last log entry is missing the container_source field. | - |
v3.5.10 | New feature | The TKE log collection feature supports Node-level metadata. Container collection supports fuzzy matching for namespaces using an asterisk (*). Added a reporting plan for the compatibility of container stdout/stderr fields. | - |
| Experience optimization | The key management tool has enhanced uniqueness validation: it automatically validates when adding/updating a key to prevent duplicate entries. Fixed the issue where, in a multi-tenant scenario, deleting and then re-adding a user causes log collection to stop. Fixed the issue where LogListener incorrectly deletes all keys when executing the `ak -a delete` command. Fixed the issue where, after the default account is deleted and re-added, the server_config directory fails to pull collection configurations. Also resolved the issue of configuration dirty data caused by heartbeat configuration pull conflicts during account deletion. Fixed the issue where, in the new architecture, the %f format fails to recognize milliseconds and microseconds during log time parsing. | - |
v3.5.9 | Experience optimization | Fixed the issue where a file was collected repeatedly as the file size calculated by the system was incorrect due to the lace of a line break at the end of the file. | - |
v3.5.8 | New feature | Supports sending aggregation. Container collection supports filtering based on standard output/standard error. | - |
| Experience optimization | Optimized the policy for using https access in the installation script mode. After optimization, the determination is made based on the port number. Fixed the issue where data points are cleaned up when the file size is 0 and no writes have occurred for an extended period. Fixed the issue where logs didn't have tag metadata due to metadata file generation delay in container scenarios. Fixed the issue of path recognition errors in TKE filePath mounted file scenarios. Fixed the empty pointer processing exception in advanced data processing. Fixed the issue where executing the check command results in a core dump. | - |
v3.5.7 | New feature | Configuration parameters for the new container architecture can be obtained from environment variables. In Linux scenarios, switching between private/public networks is supported when logs are uploaded. Dynamic IP address acquisition is supported for machine groups labeled with Label. | - |
v3.5.6 | Experience optimization | Fixed the issue where a missing parameter in the LogListener request header causes a core dump. Fixed the issue where configuration comparison errors cause frequent pipeline rebuilds. Optimized the combined parsing mode and fixed processing exceptions when the root processor was a regular expression parsing plugin. Fixed the issue of duplicate log collection when writing logs after a change from multi-line to single-line regular expressions. Fixed the issue where, if the collection path is not modified but after the log topic is modified, one log was missed during incremental collection. | - |
v3.5.5 | Experience optimization | Fixed the cross-device link error that occurred during the operator script installation when /tmp and /opt were on different file systems. | - |
v3.5.4 | Experience optimization | When a collection configuration is deleted, the point information associated with that configuration on LogListener is cleared. The maximum memory limit for LogListener in container scenarios has been adjusted to 1024 MB. After LogListener completes the point conversion, log-agent stops resource monitoring. After the new architecture installation is complete, a status code must be output, with 0 indicating success and -1 indicating failure. | - |
v3.5.3 | Experience optimization | Fixed the issue where point upgrade fails because the inode exceeds the int32 limit. Fixed the issue where the loglistener_operator reports a "text file busy" error during the upgrade process. Fixed the issue where the memory leaked as the corresponding configuration cache couldn't be cleared when a rotation file was removed. | - |
v3.5.2 | New feature | Supported HTTPS transmission encryption. | - |
v2.9.5 | Experience optimization | Fixed the exception of parsing the millisecond timestamp (`%F`). Fixed the Ubuntu startup failure. | - |
2.9.1 | Experience optimization | Supports dynamic generation of instanceID. Optimized the log parsing format pipeline. Optimized abnormal overriding during automatic upgrade. Fixed the issue where the heartbeat cannot be reported normally after an upgrade. | - |
v2.9.0 | Experience optimization | Fixed the issue where LogListener couldn't be started if the checkpoint file is corrupted. | - |
v2.8.9 | New feature | LogListener supports the Windows operating system. Supports collection of Windows Event Logs. | |
v2.8.8 | New feature | Added `meta_processor` for combined parsing and supported parsing custom metadata (path). Added support for uploading parsing-failed logs. Supports installation on CentOS 9 and later systems. | |
| Experience optimization | Optimized the blocklist feature. Now, the blocklist FILE mode supports wildcard filtering. Fixed the issue of infinite restart after an abnormal startup. Fixed the restart issue caused by configuring a regular expression rule for single-line full-text parsing. Fixed the issue where closing LogListener may cause the process to hang. | - |
v2.8.6 | Experience optimization | Fixed the abnormal automatic upgrade issue in certain scenarios. Fixed the issue where renaming too many files will cause the program to malfunction. | - |
v2.8.5 | New feature | Supported advanced configuration options for directory depth at the collection configuration level and file timeout. | - |
| Experience optimization | Fixed full disk and business exceptions caused by file handle leaks. Fixed the issue where excessive invalid logs were printed when multi-line log parsing failed. | - |
v2.8.4 | New feature | Supported parsing the time zone information in the log time. | - |
| Experience optimization | Optimized the line break processing during `hostname` extraction. Fixed the memory leak issue in certain log rotation scenarios. Fixed the garbled hostname metadata issue. Fixed the exception when multiple files were rotated at the same time. | - |
v2.8.3 | Experience optimization | Optimized the LogListener installation and stop logic. Fixed the issue where collection was blocked due to possible exceptions when an empty string was uploaded. Fixed the issue where files with a small amount of written data might be missing or delayed during collection in soft link scenarios. Optimized the issue where backtracking collection may occur during log rotation in some scenarios. Fixed the issue that removing a directory soft link affects the collection of other directory soft links that point to the same target. | - |
v2.8.2 | Experience optimization | Fixed the issue that files in a directory cannot be collected if a soft link of the directory is removed and the same soft link is created again. | - |
v2.8.1 | Experience optimization | Fixed the JSON parsing exception. Fixed the filter exception in multi-line mode and the upload exception caused by a single KV exceeding 1 MB. | - |
v2.8.0 | New feature | LogListener supports collecting log text in GBK encoding mode. | - |
v2.7.9 | Experience optimization | Added file lock validation for LogListener. By default, only one agent instance can be started. Optimized the exception handling for empty lines in containerd stdout. Optimized the issues of disk full and service abnormalities caused by file handle leaks. Optimized the issue where the latter part of the content fails to be parsed when the number of lines in multi-line logs is excessive. | - |
v2.7.8 | Experience optimization | Optimized the metadata file generation delay in container scenarios, which caused the issue of logs lacking TAG metadata. | - |
v2.7.7 | Experience optimization | Fixed the issue where the collection program's network connection could not be restored after DNS resolution exception recovery. | - |
v2.7.6 | Experience optimization | Optimized the handling of line breaks during hostname extraction. | - |
v2.7.5 | Experience optimization | Fixed the processing exception in file rotation when the actual file and soft link in the same directory were collected at the same time with different collection configurations. | - |
v2.7.4 | New feature | Supported collecting `hostname` as the metadata. Combined parsing now includes a meta_processor, which supports parsing custom metadata (path). | - |
| Experience optimization | Fixed the missing collection problem in file deletion scenarios. Fixed the issue of file re-collection caused by incorrect file size judgment due to the absence of a newline character at the end of the file. | - |
v2.7.3 | New feature | Supported log upload from multiple endpoints by a single agent instance. | - |
v2.7.2 | Experience optimization | Fixed the issue where the configuration cache corresponding to rotated files could not be cleaned up upon removal, causing a memory leak. | - |
v2.7.1 | Experience optimization | Fixed the issue where a large number of empty service logs were printed. | - |
v2.7.0 | Experience optimization | Fixed the issue where an empty string could cause an exception during PB serialization, leading to collection blockage. | - |
v2.6.9 | Experience optimization | Fixed the issue where invalid logs were excessively printed in scenarios where multi-line parsing failed. | - |
v2.6.8 | Experience optimization | Optimized the collection specification limit for LogListener. A protection mechanism is triggered when the limit is exceeded. Fixed the issue where Ubuntu fails to start on boot. Optimized the blocklist feature to reduce memory usage. Fixed the combined parsing error issue with the "processor_split_key_value" plugin. Optimized the printing of certain logs. | - |
v2.6.7 | New feature | Supported the multi-tenancy collection capabilities under a single agent. | - |
v2.6.6 | Experience optimization | Fixed the issue where files with minimal write activity under soft link scenarios might experience missed/delayed collection. | - |
v2.6.5 | New feature | Supported parsing the time zone information in the log time. | - |
| Experience optimization | Fixed the null pointer exception in advanced data processing. Fixed the abnormal issue that occurs when multiple files are rotated simultaneously. | - |
v2.6.4 | New feature | Supported customizing log parsing rules through a plugin. | |
| Experience optimization | Optimized the log parsing format pipeline. Fixed the issue with parsing the millisecond timestamp (%F) format. | - |
v2.6.3 | Experience optimization | Fixed the issue where LogListener fails to start when the checkpoint file is corrupted. Fixed the issue where the blocklist didn't take effect for new files in special scenarios. | - |
v2.6.2 | New feature | Added support for incremental collection. | - |
| Experience optimization | Optimized the issue where collection is ignored in the period from file scanning to processing. Fixed the issue where the automatic upgrade process abnormally overwrites data. | - |
v2.6.1 | Experience optimization | Fixed the issue where retroactive collection may occur during log rotation in certain scenarios. Adjusted the timeout duration for log upload on the collection end to avoid data duplication caused by timeout. | - |
v2.6.0 | New feature | Added support for CVM batch deployment. Added support for ciphertext storage of secret IDs/KEYs. | |
| Experience optimization | Optimized the LogListener install/stop logic. Optimized the retry policy upon upload failures. Added a tool for detecting and rectifying dead locks caused by Glibc libraries of earlier versions. Optimized collection performance. | - |
v2.5.9 | Experience optimization | Optimized the resource limit policy. | - |
v2.5.8 | Experience optimization | Fixed the issue where removing a directory symlink affects the collection of other directory symlinks pointing to the same target. Fixed the issue where files under a directory cannot be collected after a symlink to that directory is removed and then recreated. | - |
v2.5.7 | Experience optimization | Fixed the (new) issue that logs will be collected again when the log file size is greater than 2 GB. Fixed the issue where the program may hang when a large number of files are renamed. Fixed the issue where specified fields cannot be updated under log collection monitoring. | - |
v2.5.6 | Experience optimization | Optimized the issue that under specific use cases, the collection program cannot be triggered. | - |
v2.5.5 | Experience optimization | Optimized metadata checkpoints for collection to guarantee no data will lose due to restart. Supports resource limit configuration and overrun handling for memory, CPU, and bandwidth. | - |
v2.5.4 | New feature | Added support for log collection monitoring. | |
| Experience optimization | Enhanced memory overrun handling: LogListener will be automatically loaded when memory overrun lasts for a period of time. | - |
v2.5.3 | Performance optimization | Optimized LogListener exceptions caused by memory issues. | - |
v2.5.2 | New feature | All logs that fail to be parsed are uploaded with LogParseFailure as the Key name and the original log content as the Value. | - |
| Experience optimization | Optimized the blocklist feature, and the blocklist FILE mode now supports wildcard filtering. | - |
v2.5.1 | Experience optimization | Enhanced the handling when breakpoint metadata could not be found in the collection file. | - |
v2.5.0 | New feature | Added support for automatic LogListener upgrade. Added support for automatic LogListener start in Ubuntu operating system. | |
v2.4.6 | Experience optimization | Cleared residual configuration data in the cache after the collection configuration was changed. Optimized the issue where file collection with a soft link pointing to the `realpath` file was affected when an `IN_DELETE` event that deleted the soft link was being processed. Optimized the feature of collecting the same source file via the file's soft link and the directory's soft link at the same time. | - |
v2.4.5 | New feature | Added support for `multiline_fullregex_log` log collection. | |
v2.4.4 | Experience optimization | Optimized the issue where log collection used inaccurate log timestamps due to the msec feature. | - |
v2.4.3 | New feature | Supported automatic detection of log formats (logFormat). | - |
v2.4.2 | Experience optimization | Optimized the cache eviction issue when configurations are pulled in Tencent Cloud container scenarios. | - |
v2.4.1 | New feature | Supported millisecond-level log data collection. | - |
| Experience optimization | Optimized the operational exception caused by data without line breaks in user logs. | - |
v2.4.0 | New feature | LogListener supports process instance-level monitoring. | - |
v2.3.9 | New feature | Supported configuring a blocklist for collection paths. | - |
| Performance optimization | Fixed the memory leak caused by an excessively low version of the boost library. | - |
v2.3.8 | New feature | Supported multiple paths in collection configuration. | - |
v2.3.6 | Performance optimization | Fixed the issue where collection stops due to an invalid key value. Fixed the memory leak issue caused by a request failure that returns a 502 status code. | - |
v2.3.5 | New feature | Supported the log context search feature. | - |
| Performance optimization | Fixed the issue where, in static configuration mode, collection stops after an authentication failure is returned during log upload. Fixed the issue where dynamic configuration is no longer read after memory usage exceeds the threshold in dynamic configuration mode. Fixed the issue where duplicate collection may occasionally occur during log rotation when the log production rate is too high. Fixed the memory leak issue caused by multiple failed retries during log upload. | - |
v2.3.1 | Experience optimization | Memory limit optimization. Requests that exceed 3 seconds are marked as timed out when the memory limit is reached. | - |
v2.2.6 | New feature | Supported separate configuration of internal and public network domain names. | - |
| Performance optimization | Fixed LogListener exceptions caused by `getip`. | - |
v2.2.5 | New feature | Added support for Tencent Cloud COC environment deployment. | - |
| Experience optimization | Fixed the core issue caused by `getip`. | - |
v2.2.4 | Experience optimization | Changed the commands for installation and initialization to the subcommands `install` and `init` of `tools/loglistener.sh` respectively. Changed the command for restart to `/etc/init.d/loglistenerd start|stop|restart`. | - |
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. | - |
Earlier versions | - | v2.2.2 added support for collection by full regular expression. v2.1.4 added support for full text in multi lines. v2.1.1 added support for log structuring. | - |
Esta página foi útil?
Você também pode entrar em contato com a Equipe de vendas ou Enviar um tíquete em caso de ajuda.
comentários