Enable Logging for HTTP(S) Load Balancers

Sign in to the Google Cloud Management Console.

Select the GCP project that you want to access from the console top navigation bar.

Navigate to Load Balancing console available at https://console.cloud.google.com/net-services/loadbalancing.

Select the LOAD BALANCERS tab and click on the name (link) of the load balancer that you want to examine.

Select the DETAILS tab and examine the backend service associated with the load balancer, listed in the Backend section. Choose ADVANCED CONFIGURATIONS and check the Logging attribute value. If Logging is set to Disabled, the selected Google Cloud HTTP(S) load balancer is not configured to log all network traffic.

Repeat steps no. 4 and 5 for each load balancer available within the selected GCP project.

Repeat steps no. 2 – 6 for each project deployed in your Google Cloud Platform (GCP) account.

Run projects list command (Windows/macOS/Linux) using custom query filters to list the IDs of all the Google Cloud Platform (GCP) projects available in your Google Cloud account:

gcloud projects list
				--format="table(projectId)"

The command output should return the requested GCP project identifiers (IDs):

PROJECT_ID
				cc-project5-stack-123123
				cc-bigdata-project-112233

Run compute url-maps list command (Windows/macOS/Linux) using the ID of the GCP project that you want to examine as the identifier parameter and custom query filters to describe the name of each load balancer (identified by an URL map) created for the selected project:

gcloud compute url-maps list
				--project cc-project5-stack-123123
				--format="table(name)"

The command output should return the name(s) of the existing load balancer(s):

NAME
				cc-project5-web-load-balancer
				cc-project5-int-load-balancer

Run compute url-maps describe command (Windows/macOS/Linux) using the name of the GCP load balancer that you want to examine as the identifier parameter and custom query filters to describe the resource URL of the backend service associated with the selected load balancer:

gcloud compute url-maps describe cc-project5-web-load-balancer
				--format="value(defaultService)"

The command output should return the requested resource URL:

https://www.googleapis.com/compute/v1/projects/cc-project5-stack-123123/global/backendServices/cc-project5-web-backend-service

Run compute backend-services describe command (Windows/macOS/Linux) using the URL of the associated backend service that you want to examine as the identifier parameter and custom output filtering to describe the logging configuration status available for the selected backend service:

gcloud compute backend-services describe https://www.googleapis.com/compute/v1/projects/cc-project5-stack-123123/global/backendServices/cc-project5-web-backend-service
				--format="value(logConfig.enable)"

The command output should return the logging status set for the selected resource (True for enabled, False for disabled):

False

If the compute backend-services describe command output returns False, as shown in the example above, the selected Google Cloud HTTP(S) load balancer is not configured to log all network traffic.

Repeat steps no. 5 – 8 for each load balancer created for the selected GCP project.

Repeat steps no. 3 – 9 for each project deployed in your Google Cloud Platform (GCP) account.

Sign in to the Google Cloud Management Console.

Select the GCP project that you want to access from the console top navigation bar.

Navigate to Load Balancing console available at https://console.cloud.google.com/net-services/loadbalancing.

Select the LOAD BALANCERS tab, click on the name (link) of the load balancer that you want to configure, and choose EDIT.

Select the Backend configuration tab, choose the backend service that you want to reconfigure, and click on the pencil icon (EDIT), to modify the resource configuration.

For Logging, select the Enable logging checkbox to enable the logging feature and set the appropriate Sample rate. Sample rate specifies the sampling probability that an HTTP(S) access entry gets logged. The sampling probability is a percentage represented as a decimal point, 1.0 means 100%. You can specify a number from 0 to 1.

Choose UPDATE to save the configuration changes.

Repeat steps no. 4 – 7 for each load balancer available within the selected GCP project.

Repeat steps no. 2 – 8 for each project deployed in your Google Cloud Platform (GCP) account.

Run compute backend-services update command (Windows/macOS/Linux) to attach the new edge security policy to the backend service associated with your Google Cloud load balancer:

gcloud compute backend-services update https://www.googleapis.com/compute/v1/projects/cc-project5-stack-123123/global/backendServices/cc-project5-web-backend-service
				--enable-logging
				--logging-sample-rate=1.0

The command output should return the URL of the updated backend service:

Updated [https://www.googleapis.com/compute/v1/projects/cc-project5-stack-123123/global/backendServices/cc-project5-web-backend-service].

Repeat steps no. 1 and 2 to enable logging for each HTTP(S) load balancer deployed in the selected GCP project.

Repeat steps no. 1 – 3 for each project created within your Google Cloud Platform (GCP) account.