Home / Platform management / Clusters / Clusters / Plugin management / Deploy Clickhouse Log Storage Component (Alpha)

Deploy Clickhouse Log Storage Component (Alpha)

The log storage component is responsible for storing logs, events, and audit data collected by the log collection component from one or more clusters in the platform.

Tip:

After the log storage component is successfully deployed, the cluster where the component is deployed can be used as a storage cluster for other clusters in the platform (the storage cluster can be selected when the log collection component is deployed) to provide log storage services for itself and other clusters in the platform.
Global clusters can query log data stored on any business cluster in the platform.
In this platform, we recommend that you deploy a log storage plug-in to avoid resource conflicts between the Clickhouse log storage plug-in and the ElasticSearch log storage plug-in.
The current version of Clickhouse does not support the Jenkins pipeline execution record archiving function in Devops products.
The log storage plug-in of the current version of Clickhouse does not support the call chain logging capability of Service Mesh.

Steps

In the left navigation pane, click Cluster Management > Clusters.
Click the cluster name of the log storage component to be deployed.
On the Plugins tab, click on the right of Clickhouse Log Storage Component. > Deployment.
Configure the parameters by referring to the following instructions:

Parameter	Description
Component Deployment Settings Storage Type: LocalVolume: Local storage, log data will be stored in the local storage path of the selected node. The advantage of using this method is that the log component is directly bound to the local storage, which does not need to access the storage through the network, which can provide better storage performance. StorageClass: Dynamically creates storage resources to store log data using storage classes. When multiple storage classes are defined for the entire cluster, the administrator can select the corresponding storage class for the log component based on the usage scenario, reducing the impact of host exceptions on storage. However, the performance of StorageClass can be affected by factors such as network bandwidth and latency, and it needs to rely on the redundancy mechanisms provided by the storage backend to achieve high availability of storage. Refer to the document Storage Class .
Retention time	The maximum period of time that logs, events, and audit data can be retained on the cluster, and data beyond the retention period will be automatically cleared. Tip: You can back up the data that you need to retain for a long time, if you need help, please contact technical support

Parameter

Description

Component Deployment Settings

Storage Type:
- LocalVolume: Local storage, log data will be stored in the local storage path of the selected node. The advantage of using this method is that the log component is directly bound to the local storage, which does not need to access the storage through the network, which can provide better storage performance.
- StorageClass: Dynamically creates storage resources to store log data using storage classes. When multiple storage classes are defined for the entire cluster, the administrator can select the corresponding storage class for the log component based on the usage scenario, reducing the impact of host exceptions on storage. However, the performance of StorageClass can be affected by factors such as network bandwidth and latency, and it needs to rely on the redundancy mechanisms provided by the storage backend to achieve high availability of storage. Refer to the document Storage Class .

Retention time

The maximum period of time that logs, events, and audit data can be retained on the cluster, and data beyond the retention period will be automatically cleared.
Tip: You can back up the data that you need to retain for a long time, if you need help, please contact technical support

Click Deploy.