Term | Resource Type | Description |
tke-log-agent | DaemonSet | Each log-agent Pod contains a controller container and a loglistener sidecar container, responsible for collecting logs generated by all containers on the node. |
cls-provisioner | Deployment | One instance per cluster, responsible for converting CRD configurations into collection configurations that loglistener can understand and communicating with CLS. |
logconfigs.cls.cloud.tencent.com | CRD | - |
Category | Content |
Feature | It is fully released in all overseas regions, and it is in full grayscale release in domestic regions except Beijing, Shanghai, and Guangzhou. journal log collection is supported. LogListener supports password-free authentication. Supports the processor_add_fields plugin for adding fields and the processor_desensitize plugin for data masking. The collection time supports nanosecond precision. |
Category | Content |
Feature | It is fully released in all overseas regions. The CLS new architecture collector version is released in grayscale. |
Category | Content |
Feature | The log component supports X86 and ARM nodes. Fixed an issue where metadata generation failed in multi-path collection scenarios. |
Category | Content |
Feature | Supports log collection in the Riyadh region. |
Category | Content |
Feature | TKE log collection supports collecting Node Labels as log metadata. The machine group name length limit is consistent with the CLS API, with a length of 255 characters. |
Bugfix | Fix the issue where collection directories cannot be correctly identified in container file collection scenarios when multiple paths have nested mounts. |
Category | Content |
Feature | Added a fallback policy for the environment variable POD_IP. |
Bugfix | Fixed an issue where Kafka log shipping failed to collect logs from other subdirectories due to the absence of the subdirectory in the collection path. Fixed an issue of the path mapping exception caused by the concurrent modification of collection rules. |
Category | Content |
Feature | Added the MAX_SEND_RETRY_TIME environment variable to support the max_send_retry_time parameter of loglistener. Remove the validation of Pod IP address by environment variables. |
Bugfix | - |
Category | Content |
Feature | - |
Bugfix | Fixed the issue where custom parameters did not take effect when the Kafka collector was configured with both rdKafka custom parameters and the raw output format. |
Category | Content |
Feature | Consumer-side Kafka supports log collection and reporting of original logs. |
Bugfix | Fixed the log collection delay issue caused by Pod event processing failures without retries in extreme scenarios. |
Category | Content |
Feature | - |
Bugfix | Fixed an issue where the Kafka collector encountered livenessProbe failures when the node CPU was under high load. Fixed an issue where logs collected by the Kafka collector under the containerd runtime carried a CRI format prefix. |
Category | Content |
Feature | cls-provisioner supports the vmagent container. By default, log-agent generates the loglistener configuration file in encrypted mode. |
Bugfix | - |
Category | Content |
Feature | cls-provisioner supports enabling dynamic indexing when a topic is created. cls-provisioner supports adding a finalizer to logconfig. Added the max_metadata_wait_time_s parameter to loglistener, which can be configured through an environment variable. When the key-value index is text, the tokenizer can be empty. |
Bugfix | Fixed an issue in log-agent where containers were incorrectly identified during metadata generation. For example, different containers of the same pod can both have a /data path, such as container A with a volume mounted at /data and container B with a regular directory named /data. Fixed an issue in cls-provisioner where residual dirty data might remain when a switch is performed between host_file and container_file. Fixed an issue where collection configuration synchronization was deleted or overwritten in self-built mode. Fixed an issue where the Kafka collector could not obtain the latest metadata of the target, and added a mechanism for periodically updating metadata. Fixed an issue where different collection rules collected different files in the same directory, causing metadata to not be generated as expected. |
Category | Content |
Feature | The Kafka collector supports custom metadata. The Kafka collector supports outputting metadata in string format. Added the cluster_id field to the Kafka collector metadata. Supports advanced filters. |
Bugfix | Fixed resource compatibility issues in existing components. Added support for regions without CLS services by configuring CLOUD_API_REGION in components. Added docker DataRoot to log-agent to prevent the standard docker runtime from triggering dynamic mounts. Adapted the standard output path mapping for clusters below version 1.14. log-agent no longer automatically mounts the docker dataroot. Fixed an issue where file events could not be processed because retryChan was full. Fixed an issue where standard output logs could not be collected due to a new addition with an empty containerOpt. Fixed an issue where frequent namespace updates caused cls-provisioner OOM. |
Category | Content |
Feature | The log component exposes metrics related to collection rule status, with the default port being 8088. |
Bugfix | - |
Category | Content |
Feature | Switch elastic pod cls-provisioner to norm authentication. |
Bugfix | Fix the issue of paths being mistakenly deleted due to multipath. |
Category | Content |
Feature | TKE multi-path collection supports path wildcards. |
Bugfix | Fixed the issue where log loss occurred because kubelet failed to map the standard data log path for clusters earlier than version 1.19. |
Category | Content |
Feature | Add a source resource when creating a collection configuration to distinguish TKE collection configurations, the CLS console, and direct redirects to TKE. Supports namespaces and regular expressions for excluded namespaces. Add an advanced collection configuration to collect ClsAgentParseFailMerge, and modify the parameter type to fix parameter loss during JSON marshal/unmarshal. Supports custom installation namespaces for cls-provisioner and log-agent, with kube-system as the default. Supports multi-path collection from container files and host files. |
Bugfix | Fixed an issue where log-agent did not delete soft links when job pods ended, causing the number of files and directories monitored by loglistener to reach the upper limit. Fixed an issue where kafkaListener failed to collect logs due to excessively long single-line logs. Updated the maximum single-line length to 2 MB. Fixed an issue where mapping the log directory failed when the PVC StorageClass was empty. |
Category | Content |
Feature | - |
Bugfix | Fixed the issue that occurred when log-agent processed the container notin inverse selection logic. |
Category | Content |
Feature | Add AdvancedConfig, and add the MaxDepth and FileTimeout parameters. Add the HotPeriod parameter to support the transition rule for moving data from standard topics to infrequent access storage. Supports container selection and exclusion, collection of selected container metadata, and collection of selected tags. |
Bugfix | Fixed an issue where removing prefixes from blocklist paths was abnormal. Fixed an issue where log-agent encountered a problem when the Pod remained unchanged but the soft link was deleted and recreated. Fixed an issue where cls-provisioner panicked because it could not find the topic. Added validation for logconfig. Invalid logconfigs are not processed to avoid program panics or processing errors. |
Category | Content |
Feature | - |
Bugfix | Fixed the issue where retries were no longer attempted after workload became unsupported. |
Category | Content |
Feature | Add the logConfig-max-threshold parameter. When the number of logconfigs reaches a certain threshold, upgrades or restarts use an informer to query workload information. Optimize the method for obtaining the docker root, and add a method that obtains it through the api first. Kafka collection supports custom metadata and SASL authentication. |
Bugfix | Fixed an issue where log-agent obtained incorrect kubelet parameters during startup. Fixed an error in the API call for obtaining the logset when the topicID is replaced. CLS is case-insensitive. Fixed a case sensitivity issue in cls-provisioner. By default, log-agent supports CSI and no longer separately determines and compares the Provisioner of StorageClasses. |
Category | Content |
Feature | Added support for multiline collection regex matching in the Kafka collector for container standard output. Add the tag TencentCloud API address configuration to the environment variable. |
Bugfix | In regions without CLS services, such as Shenzhen and Tianjin, the agent failed to automatically create a topic for synchronizing cluster tags. Fixed an issue where the Kafka collector metadata prefix captured the containerd format. Fixed an issue where cls-provisioner omitted the incremental and full sync options when synchronizing CLS. During logconfig loading, workload information is queried through an informer to reduce the load on the apiserver. |
Category | Content |
Feature | CLS delivery regions now include Sao Paulo and the Shanghai Autonomous Driving Zone. |
Bugfix | - |
Category | Content |
Feature | Collection of init container standard output logs is supported. GBK encoding is supported for CLS log parsing. CLS log collection rules support namespace label selectors. |
Bugfix | Fixed an issue where the event queue was retried frequently. Optimize the processing queue algorithm for Logconfig and pods in log-agent to prevent the queue from being blocked by a large number of duplicate events. Fixed an issue where standard output container logs were not collected when only a namespace was specified without a label. |
Category | Content |
Feature | CLS Infrequent Access storage supports index configuration. |
Bugfix | - |
Category | Content |
Feature | CLS collection rules in container file and host file scenarios support blocklist configuration. |
Bugfix | - |
Category | Content |
Feature | loglistener supports the use of multiple CPU cores. loglistener memory supports adaptive loglistener limit settings, with the limit mem 100M set as the maximum memory usage for loglistener. |
Bugfix | Fixed the issue where log-agent did not handle error returns when updating volume links, causing update failures to not be retried. |
Category | Content |
Feature | When automatically creating a topic, CLS log supports inheriting TKE cluster tags. Cross-region CLS log delivery is supported. |
Bugfix | - |
Category | Content |
Feature | - |
Bugfix | Fixed an issue where an empty topic id during topic replacement caused the logconfig to be deleted and recreated. Fixed an issue where logconfigpro synchronization hung because the logconfigpro informer was not started. |
Category | Content |
Feature | By default, log collection from loglistener in kube-system is blocked. Index creation policy update: A default index is created only when a topic is automatically created. In other scenarios, the topic index is not modified. Supports adding metadata to messages in the Kafka collector. Supports the following parsing modes for the Kafka collector: single-line full text, JSON, and multi-line full text. |
Bugfix | Fixed an issue where the container could not be specified when standard output is collected in workload scenarios. Add a docker client and obtain the Storage Driver. If the configuration file does not contain it, obtain the info through the client to get the Storage Driver. Fixed an issue where an incorrect metadatalabel was specified when container files were collected. Fixed the solution for obtaining the kubelet root directory. Fixed an issue where an incorrect prefix setting when old collection configurations were deleted caused collection configuration matching errors. Fixed an issue where the timestampKey timestamp configured for messages in the current Kafka collector did not take effect. |
Category | Content |
Feature | When creating a topic, cls-provisioner supports specifying key-value indexes, including the index name, type, tokenizer, and whether to enable statistics. If this is not supported, the pod_name, namespace, and container_name indexes are enabled by default. Specifying metadatalabels is supported, which writes the specified pod labels to metadata collection. If this is not supported, all pod labels are collected as metadata. Supports customizing the backend address of the CLS TencentCloud API service. |
Bugfix | - |
Category | Content |
Feature | log-agent supports user-defined modification of the kubelet root directory and the docker root directory. |
Bugfix | - |
Category | Content. |
Feature | Log collection configuration supports the label != operator (exclude labels).Supports Log Service collecting only incremental logs. Log collection configuration supports selecting multiple namespaces and excluding namespaces. log-agent supports configuring pod labels with the same Key but different values. loglistener supports configurable parameters. |
Bugfix | Fixed known issues when log-agent uses a configmap as the source. Fixed an issue where validation failed because the collector configuration was empty under certain conditions. Fixed an issue where the collector failed to delete the configuration when a log rule was deleted. Resolved compatibility issues with logConfig configuration. |
Category | Content |
Feature | The interface used by cls-provisioner to access CLS is switched to TencentCloud API. Supports TKE log collection delivery to ckafka. |
Bugfix | - |
Category | Content |
Feature | - |
Bugfix | Fixed the issue where one Pod corresponds to multiple logconfigs. |
Category | Content |
Feature | - |
Bugfix | Fixed the issue where the extraction mode set by users on the topic was overwritten in some scenarios. |
Category | Content |
Feature | - |
Bugfix | Fixed the issue where metadata could not be created in some cases when collection configurations of the stdout type were deleted. |
Category | Content |
Feature | - |
Bugfix | Fixed an issue where log-agent panicked under certain conditions. Fixed an issue where workload caching caused soft link deletion. Fixed an issue where metadata file creation failed. |
Category | Content |
Feature | - |
Bugfix | Fixed an issue where metadata was accidentally deleted during container restart in a pod. Before log-agent starts, it automatically cleans LogAgentRootDir to prevent contamination by dirty data. Fixed a log-agent component panic caused by extreme scenarios. Fixed a startup failure caused by log-agent repeatedly mounting the /data directory. |
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan