Enabling Logging

Constraints

• This add-on is available only for Huawei Cloud clusters or on-premises clusters v1.21 or later.
• A maximum of 50 log collection rules can be configured for each cluster.
• This add-on cannot collect .gz, .tar, and .zip logs.
• If the node storage driver is Device Mapper, the container file logs must be collected from the path where the data disk is attached to the node.
• If the container runtime is containerd, each standard output log cannot be in multiple lines. (This does not apply to log-agent v1.3.0 or later.)
• In each cluster, up to 10,000 single-line logs can be collected per second, and up to 2,000 multi-line logs can be collected per second.
• On each node, up to 4,096 logs can be collected.
• If a volume is attached to the data directory of a service container, this add-on cannot collect data from the parent directory. In this case, you need to configure a complete data directory.
• The container running time must be longer than 1 minute for log collection to prevent logs from being deleted too quickly.

Billing

LTS does not charge you for creating log groups and offers a free quota for log collection every month. You pay only for log volume that exceeds the quota.

A network access mode is required for an on-premises cluster. If you select Direct Connect or VPN, the VPC endpoint will be billed based on how long you use it.

Log Collection

1. Log in to the UCS console, choose Fleets, and click the fleet name to access the fleet details page.
2. Choose Container Clusters, click the cluster name to access the cluster details page, and choose Logging.
3. (Only for Huawei Cloud clusters) If you are not authorized, obtain required permissions first. In the displayed dialog box, click Authorize.
4. (Only for Huawei Cloud clusters) Click Enable and wait for about 30 seconds until the log page is automatically displayed.

   

   • Standard output logs: A log collection policy named default-stdout will be created, and standard output logs in all namespaces will be reported to LTS.
   • Kubernetes events: A log collection policy named default-event will be created, and Kubernetes events in all namespaces will be reported to LTS.

5. (Only for on-premises clusters) Obtain permissions required by the cloud native logging add-on. For details, see Assigning Authorization for log-agent in Your On-Premises Cluster.
6. (Only for on-premises clusters) Click Enable. In the displayed dialog box, configure log collection and network parameters. Wait for about 30 seconds until the log page is automatically displayed.

   Table 1 Log collection configuration and network configuration of on-premises clusters

   Configuration	Description
   Log collection	Standard output logs: A log collection policy named default-stdout will be created, and standard output logs in all namespaces will be reported to LTS. Kubernetes events: A log collection policy named default-event will be created, and Kubernetes events in all namespaces will be reported to LTS and AOM. Kubernetes audit logs: Kubernetes audit logs will be collected and reported to LTS. kube-apiserver logs: Logs of the kube-apiserver component on the control plane will be collected and reported to LTS. kube-controller-manager logs: Logs of the kube-controller-manager component on the control plane will be collected and reported to LTS. kube-scheduler logs: Logs of the kube-scheduler component on the control plane will be collected and reported to LTS.
   Network	Public network: This option features flexibility, cost-effectiveness, and easy access. It is only available for clusters that can access the public network. Direct Connect or VPN: After you connect an on-premises data center to a VPC over Direct Connect or VPN, you can use a VPC endpoint to access CIA over the private network. This option features high speed, low latency, and high security. For details, see Using Direct Connect or VPN to Report Logs of On-Premises Clusters.

Troubleshooting

All components except log-operator are not ready, and the volume failed to be attached to the node.

Solution: Check the logs of log-operator. During add-on installation, the configuration files required by other components are generated by log-operator. If the configuration files are invalid, all components cannot be started.