Docs

Volcengine Kubernetes Engine

Historical announcements

[Product changes] Container logs key value and index fields changes description

To better support the collection capability of the container log, the Volcengine Kubernetes Engine (VKE) will upgrade the log-collector add-on. After the upgrade, changes will be made to the key values and index fields of the container log, thus influencing all the features involving log query (such as log query, log dashboard, and log alert).

tip

If you have not installed the log-collector add-on in any cluster, then the changes will not influence you.

You need to manually upgrade or install the log-collector add-on. If you do not upgrade or install this add-on, then the key values and index of the container log will not change.

The changes will not impact the real-time log features of the container. They will not involve log features such as Kubernetes events and audits, and will only affect relevant container log features that integrate VKE and Torch Log Service (TLS).

For the upgrade records of the log-collector add-on, refer to log-collector.

Detailed changes to the key-value indexed fields in container logs

tip

The changes made to the key-value indexed fields in the container log of the VKE Pod are as follows. For the details about the key values and index fields of the container log of the VCI Pod, refer to VCI [Product changes].

Key value and index field of the container log			Changed	Description
Previous versions (before version 1.2.0)	New versions (version 1.2.0 and later)		Changed	Description
cluster_id	cluster_id	No, there are not.	The ID of the cluster to which Pod belongs.
__source__	__source__	No, there are not.	The IP address of the log source server.
host_ip	host_ip	No, there are not.	The IP of the host to which Pod belongs, which is the Node IP.
container_source	__container_source__	Yes, there are changes.	Log source.
namespace	__namespace__	Yes, there are changes.	Name of the namespace to which Pod belongs
pod_ip	__container_ip__	Yes, there are changes.	Pod (container group) IP.
pod_name	__ pod_name__	Yes, there are changes.	Pod name.
pod_uid	__ pod_uid__	Yes, there are changes.	The only label of Pod.
container_name	__container_name__	Yes, there are changes.	Container name.
image_name	__image_name__	Yes, there are changes.	Image name.
content	__content__	Yes, there are changes.	Contents of the logs.

Changes impact

Log query

This upgrade influences the console query, API query, alert query, and dashboard query of the container log.

tip

The key-value indexed fields changed in this upgrade cannot be queried across the upgrade time point. However, if you need the queries to span across the upgrade time point anyway, submit a TLS ticket.

If you need to query the historical data of the log-collector add-on of version 1.2.0 and earlier, you need to use the field names of the earlier versions. Meanwhile, the data must be from any time period before this upgrade. An example is as follows:

pod_ip:"172.**.**.**" |select count(*) AS num

If you need to query the new logs of the log-collector add-on of Version 1.2.0 and later, you need to use the field names of the new versions. Meanwhile, the data's timeline scope should be any time after this upgrade. An example is as follows:

__container_ip__:"172.**.**.**" |select count(*) AS num

When it comes to the retrieval of the built-in metadata fields, such as__pod_name__, you need to carry out retrievals through the __pod_name__: "*****" format. The keyword retrieval of the full text is not supported.

Cost description

This upgrade does not incur additional costs.

Last updated: 2026.04.15 16:29:13