Connect audit logging

This document describes audit logging for Connect. Google Cloud servicesgenerate audit logs that record administrative and access activities within your Google Cloud resources.For more information about Cloud Audit Logs, see the following:

Service name

Connect audit logs use the service namegkeconnect.googleapis.com.Filter for this service:

protoPayload.serviceName="gkeconnect.googleapis.com"

Methods by permission type

Connect audit logs are enabled by turning on audit logging forgkehub.googleapis.com.

Each IAM permission has atype property, whose value is an enumthat can be one of four values:ADMIN_READ,ADMIN_WRITE,DATA_READ, orDATA_WRITE. When you call a method,Connect generates an audit log whose category is dependent on thetype property of the permission required to perform the method.Methods that require an IAM permission with thetype property valueofDATA_READ,DATA_WRITE, orADMIN_READ generateData Access audit logs.Methods that require an IAM permission with thetype property valueofADMIN_WRITE generateAdmin Activity audit logs.

API methods in the following list that are marked with (LRO) are long-running operations (LROs).These methods usually generate two audit log entries: one when the operation starts andanother when it ends. For more information seeAudit logs for long-running operations.
Permission typeMethods
DATA_READgoogle.cloud.gkeconnect.v1.EgressService.Egress
google.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 togoogle.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:No.
  • 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 togoogle.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:No.
  • Filter for this method: protoPayload.methodName="google.cloud.gkeconnect.v1beta1.EgressService.Egress"

Kubernetes audit logging

In addition to Cloud Audit Logs,Kubernetes audit logging providesa way for administrators to retain, query, process, and alert on events thatoccur in registered clusters. Administrators can use the logged information todo forensic analysis and real-time alerting, or for cataloging how a fleet ofclusters are being used and by whom.

The Connect Agent talks to the local API server running in the registeredcluster, and each cluster will have its own set of Kubernetes audit logs. Allactions that users perform from the UI through Connect are loggedby that cluster.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.