Configuration Item | Description |
Range | Data plane (gateway and Istio proxy sidecar) for which access log outputting is enabled. You can enable access logs of all data planes of a specific gateway and namespace or all data planes of the mesh to be outputted to standard outputs of containers. |
Output format | Output fields and templates of access logs. The fields output in the default format are the fields output by Istio by default. Compared with the fields output in the default format, the fields output in the enhanced format are added with Trace ID. |
Consumer end | Configure to collect access logs from the standard outputs of data plane containers to CLS. You need to select a CLS logset and log topic for storing access logs. You can choose to automatically create a logset/topic, or associate an existing logset/topic. An automatically created logset is named in the format of {mesh ID} . The name of an automatically created log topic contains a Tencent Cloud Mesh identifier, that is, the log topic is named in the format of {mesh ID}-accesslog . After the request for enabling collection of access logs to CLS is submitted, the log collection feature is enabled on clusters managed by the mesh. Then, you need to deploy the log collection component tke-log-agent (DaemonSet) on the clusters managed by the mesh, and configure collection rules and indexes of Tencent Cloud Mesh's access logs. This feature is based on the log collection feature. Ensure that CLS has been activated, and that the service role TKE_QCSRole of TKE has been associated with the preset policy QcloudAccessForTKERoleInOpsManagement for operations management of CLS. For more information, see Description of Role Permissions Related to Service Authorization |
kubectl -n {Namespace} logs {Pod name} -c istio-proxy --tail 5
Was this page helpful?