每個 IAM 權限都有 type 屬性，其值為列舉，可以是下列四個值之一：ADMIN_READ、ADMIN_WRITE、DATA_READ 或 DATA_WRITE。呼叫方法時，Connect 會產生稽核記錄，其類別取決於執行方法所需的權限 type 屬性。如果方法需要 IAM 權限，且 type 屬性值為 DATA_READ、DATA_WRITE 或 ADMIN_READ，就會產生「資料存取」稽核記錄。需要 IAM 權限且 type 屬性值為 ADMIN_WRITE 的方法會產生管理員活動稽核記錄。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-01 (世界標準時間)。"],[],[],null,["This document describes audit logging for Connect. Google Cloud services\ngenerate audit logs that record administrative and access activities within your Google Cloud resources.\nFor more information about Cloud Audit Logs, see the following:\n\n- [Types of audit logs](/logging/docs/audit#types)\n- [Audit log entry structure](/logging/docs/audit#audit_log_entry_structure)\n- [Storing and routing audit logs](/logging/docs/audit#storing_and_routing_audit_logs)\n- [Cloud Logging pricing summary](/stackdriver/pricing#logs-pricing-summary)\n- [Enable Data Access audit logs](/logging/docs/audit/configure-data-access)\n\n\u003cbr /\u003e\n\nService name\n\nConnect audit logs use the service name `gkeconnect.googleapis.com`.\nFilter for this service: \n\n```gdscript\n protoPayload.serviceName=\"gkeconnect.googleapis.com\"\n \n```\n\n\u003cbr /\u003e\n\nMethods by permission type Connect audit logs are enabled by turning on audit logging for `gkehub.googleapis.com`.\n\nEach IAM permission has a `type` property, whose value is an enum\nthat can be one of four values: `ADMIN_READ`, `ADMIN_WRITE`,\n`DATA_READ`, or `DATA_WRITE`. When you call a method,\nConnect generates an audit log whose category is dependent on the\n`type` property of the permission required to perform the method.\n\nMethods that require an IAM permission with the `type` property value\nof `DATA_READ`, `DATA_WRITE`, or `ADMIN_READ` generate\n[Data Access](/logging/docs/audit#data-access) audit logs.\n\nMethods that require an IAM permission with the `type` property value\nof `ADMIN_WRITE` generate\n[Admin Activity](/logging/docs/audit#admin-activity) audit logs.\n\n| Permission type | Methods |\n|-----------------|----------------------------------------------------------------------------------------------------------|\n| `DATA_READ` | `google.cloud.gkeconnect.v1.EgressService.Egress` `google.cloud.gkeconnect.v1beta1.EgressService.Egress` |\n\nAPI interface audit logs\n\nFor information about how and which permissions are evaluated for each method,\nsee the Identity and Access Management documentation for Connect.\n\n`google.cloud.gkeconnect.v1.EgressService`\n\nThe following audit logs are associated with methods belonging to\n`google.cloud.gkeconnect.v1.EgressService`.\n\n`Egress`\n\n- **Method** : `google.cloud.gkeconnect.v1.EgressService.Egress` \n- **Audit log type** : [Data access](/logging/docs/audit#data-access) \n- **Permissions** :\n - `gkehub.endpoints.connect - DATA_READ`\n- **Method is a long-running or streaming operation** : No. \n- **Filter for this method** : `\n protoPayload.methodName=\"google.cloud.gkeconnect.v1.EgressService.Egress\"\n ` \n\n`google.cloud.gkeconnect.v1beta1.EgressService`\n\nThe following audit logs are associated with methods belonging to\n`google.cloud.gkeconnect.v1beta1.EgressService`.\n\n`Egress`\n\n- **Method** : `google.cloud.gkeconnect.v1beta1.EgressService.Egress` \n- **Audit log type** : [Data access](/logging/docs/audit#data-access) \n- **Permissions** :\n - `gkehub.endpoints.connect - DATA_READ`\n- **Method is a long-running or streaming operation** : No. \n- **Filter for this method** : `\n protoPayload.methodName=\"google.cloud.gkeconnect.v1beta1.EgressService.Egress\"\n ` \n\nKubernetes audit logging\n\nIn addition to Cloud Audit Logs, [Kubernetes audit logging](https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/) provides\na way for administrators to retain, query, process, and alert on events that\noccur in registered clusters. Administrators can use the logged information to\ndo forensic analysis and real-time alerting, or for cataloging how a fleet of\nclusters are being used and by whom.\n\nThe Connect Agent talks to the local API server running in the registered\ncluster, and each cluster will have its own set of Kubernetes audit logs. All\nactions that users perform from the UI through Connect are logged\nby that cluster."]]
