This document describes audit logging for Connect. Google Cloud services generate audit logs that record administrative and access activities within your Google Cloud resources. For more information about Cloud Audit Logs, see the following:
- Types of audit logs
- Audit log entry structure
- Storing and routing audit logs
- Cloud Logging pricing summary
- Enable Data Access audit logs
Service name
Connect audit logs use the service name gkeconnect.googleapis.com.
Filter for this service:
protoPayload.serviceName="gkeconnect.googleapis.com"
Methods by permission type
Each IAM permission has a type property, whose value is an enum
that can be one of four values: ADMIN_READ, ADMIN_WRITE,
DATA_READ, or DATA_WRITE. When you call a method,
Connect generates an audit log whose category is dependent on the
type property of the permission required to perform the method.
Methods that require an IAM permission with the type property value
of DATA_READ, DATA_WRITE, or ADMIN_READ generate
Data Access audit logs.
Methods that require an IAM permission with the type property value
of ADMIN_WRITE generate
Admin Activity audit logs.
| Permission type | Methods |
|---|---|
DATA_READ |
google.cloud.gkeconnect.v1.EgressService.Egressgoogle.cloud.gkeconnect.v1beta1.EgressService.Egress |
API interface audit logs
For information about how and which permissions are evaluated for each method, see the Identity and Access Management documentation for Connect.
google.cloud.gkeconnect.v1.EgressService
The following audit logs are associated with methods belonging to
google.cloud.gkeconnect.v1.EgressService.
Egress
- Method:
google.cloud.gkeconnect.v1.EgressService.Egress - Audit log type: Data access
- Permissions:
gkehub.endpoints.connect - DATA_READ
- Method is a long-running or streaming operation:
Streaming RPC
- Filter for this method:
protoPayload.methodName="google.cloud.gkeconnect.v1.EgressService.Egress"
google.cloud.gkeconnect.v1beta1.EgressService
The following audit logs are associated with methods belonging to
google.cloud.gkeconnect.v1beta1.EgressService.
Egress
- Method:
google.cloud.gkeconnect.v1beta1.EgressService.Egress - Audit log type: Data access
- Permissions:
gkehub.endpoints.connect - DATA_READ
- Method is a long-running or streaming operation:
Streaming RPC
- Filter for this method:
protoPayload.methodName="google.cloud.gkeconnect.v1beta1.EgressService.Egress"
Kubernetes audit logging
In addition to Cloud Audit Logs, Kubernetes audit logging provides a way for administrators to retain, query, process, and alert on events that occur in registered clusters. Administrators can use the logged information to do forensic analysis and real-time alerting, or for cataloging how a fleet of clusters are being used and by whom.
The Connect Agent talks to the local API server running in the registered cluster, and each cluster will have its own set of Kubernetes audit logs. All actions that users perform from the UI through Connect are logged by that cluster.