Configure VPC Flow Logs

Console

1. In the Google Cloud console, go to the VPC networks page.

   Go to VPC networks

2. Click the network where you want to add a subnet.

3. Click Add subnet.

4. For Flow logs, select On.

5. Optional: Adjust the Aggregation interval and any of the following settings in the Advanced settings section:

   • Whether to configure log filtering. By default, Keep only logs that match a filter is deselected.
   • Whether to include metadata in the final log entries. By default, Metadata annotations includes all fields.
   • The Secondary sampling rate. 50% means that half of entries generated by the primary flow log sampling process are kept. The primary flow log sampling rate isn't configurable. For more information, see Log sampling and processing.

6. Populate other fields as appropriate.

7. Click Add.

gcloud

1. In the Google Cloud console, activate Cloud Shell.

   Activate Cloud Shell

   At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.

2. Run the following command:

   gcloud compute networks subnets create SUBNET_NAME \
      --enable-flow-logs \
      [--logging-aggregation-interval=AGGREGATION_INTERVAL] \
      [--logging-flow-sampling=SAMPLE_RATE] \
      [--logging-filter-expr=FILTER_EXPRESSION] \
      [--logging-metadata=LOGGING_METADATA] \
      [--logging-metadata-fields=METADATA_FIELDS] \
      [other flags as needed]
   

   Replace the following:

   • AGGREGATION_INTERVAL: the aggregation interval for flow logs in that subnet. The interval can be set to any of the following: 5-sec (default), 30-sec, 1-min, 5-min, 10-min, or 15-min.
   • SAMPLE_RATE: the secondary flow sampling rate. Secondary flow sampling can be set from 0.0 (no sampling) to 1.0 (all logs). Default is 0.5. For more information, see Log sampling and processing.
   • FILTER_EXPRESSION: an expression that defines which logs you want to keep. The expression has a limit of 2,048 characters. For details, see Log filtering.

   • LOGGING_METADATA: the metadata annotations that you want to include in the logs:

     • Use include-all to include all metadata annotations.
     • Use exclude-all to exclude all metadata annotations (default).
     • Use custom to include a custom list of metadata fields that you specify in METADATA_FIELDS.

   • METADATA_FIELDS: a comma-separated list of metadata fields you want to include in the logs. For example, src_instance,dst_instance. Can be set only if LOGGING_METADATA is set to custom.

API

Enable VPC Flow Logs when you create a new subnet.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/subnetworks
{
  "logConfig": {
    "aggregationInterval": "AGGREGATION_INTERVAL",
    "flowSampling": SAMPLING_RATE,
    "filterExpr": EXPRESSION,
    "metadata": METADATA_SETTING,
    "metadataFields": METADATA_FIELDS,
    "enable": true
  },
  "ipCidrRange": "IP_RANGE",
  "network": "NETWORK_URL",
  "name": "SUBNET_NAME"
}

Replace the following:

• PROJECT_ID: the ID of the project where the subnet will be created.
• REGION: the region where the subnet will be created.
• AGGREGATION_INTERVAL: the aggregation interval for flow logs in the subnet. The interval can be set to any of the following: INTERVAL_5_SEC, INTERVAL_30_SEC, INTERVAL_1_MIN, INTERVAL_5_MIN, INTERVAL_10_MIN, or INTERVAL_15_MIN.
• SAMPLING_RATE: the flow sampling rate. Flow sampling can be set from 0.0 (no sampling) to 1.0 (all logs). Default is .0.5.
• EXPRESSION: the filter expression you use to filter which logs are actually written. The expression has a limit of 2,048 characters. For details, see Log filtering.

• METADATA_SETTING: the metadata annotations that you want to include in the logs:

  • Use INCLUDE_ALL_METADATA to include all metadata annotations.
  • Use EXCLUDE_ALL_METADATA to exclude all metadata annotations (default).
  • Use CUSTOM_METADATA to include a custom list of metadata fields that you specify in METADATA_FIELDS.

• METADATA_FIELDS: the metadata fields you want to capture when you have set metadata: CUSTOM_METADATA. This is a comma-separated list of metadata fields, such as src_instance, src_vpc.project_id.

• IP_RANGE: the primary internal IP address range of the subnet.

• NETWORK_URL: the Virtual Private Cloud network URL where the subnet will be created.

• SUBNET_NAME: a name for the subnet.

For more information, refer to the subnetworks.insert method.

Terraform

You can use a Terraform module to create a custom mode VPC network and subnets.

The following example creates three subnets as follows:

• subnet-01 has VPC Flow Logs disabled. When you create a subnet, VPC Flow Logs are disabled unless you explicitly enable them.
• subnet-02 has VPC Flow Logs enabled with the default flow log settings.
• subnet-03 has VPC Flow Logs enabled with some custom settings.

module "test-vpc-module" {
  source       = "terraform-google-modules/network/google"
  version      = "~> 9.0"
  project_id   = var.project_id # Replace this with your project ID in quotes
  network_name = "my-custom-mode-network"
  mtu          = 1460

  subnets = [
    {
      subnet_name   = "subnet-01"
      subnet_ip     = "10.10.10.0/24"
      subnet_region = "us-west1"
    },
    {
      subnet_name           = "subnet-02"
      subnet_ip             = "10.10.20.0/24"
      subnet_region         = "us-west1"
      subnet_private_access = "true"
      subnet_flow_logs      = "true"
    },
    {
      subnet_name               = "subnet-03"
      subnet_ip                 = "10.10.30.0/24"
      subnet_region             = "us-west1"
      subnet_flow_logs          = "true"
      subnet_flow_logs_interval = "INTERVAL_10_MIN"
      subnet_flow_logs_sampling = 0.7
      subnet_flow_logs_metadata = "INCLUDE_ALL_METADATA"
      subnet_flow_logs_filter   = "false"
    }
  ]
}

To learn how to apply or remove a Terraform configuration, see Basic Terraform commands.

Console

1. In the Google Cloud console, go to the VPC networks page.

   Go to VPC networks

2. Click the subnet that you want to update.

3. Click Edit.

4. For Flow logs, select On.

5. Optional: Adjust the Aggregation interval and any of the following settings in the Advanced settings section:

   • Whether to configure log filtering. By default, Keep only logs that match a filter is deselected.
   • Whether to include metadata in the final log entries. By default, Metadata annotations includes all fields.
   • The Secondary sampling rate. 50% means that half of entries generated by the primary flow log sampling process are kept. The primary flow log sampling rate isn't configurable. For more information, see Log sampling and processing.

6. Click Save.

gcloud

1. In the Google Cloud console, activate Cloud Shell.

   Activate Cloud Shell

   At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.

2. Run the following command:

   gcloud compute networks subnets update SUBNET_NAME \
      --enable-flow-logs \
      [--logging-aggregation-interval=AGGREGATION_INTERVAL] \
      [--logging-flow-sampling=SAMPLE_RATE] \
      [--logging-filter-expr=FILTER_EXPRESSION] \
      [--logging-metadata=LOGGING_METADATA] \
      [--logging-metadata-fields=METADATA_FIELDS] \
      [other flags as needed]
   

   Replace the following:

   • AGGREGATION_INTERVAL: the aggregation interval for flow logs in that subnet. The interval can be set to any of the following: 5-sec (default), 30-sec, 1-min, 5-min, 10-min, or 15-min.
   • SAMPLE_RATE: the secondary flow sampling rate. Secondary flow sampling can be set from 0.0 (no sampling) to 1.0 (all logs). Default is 0.5. For more information, see Log sampling and processing.
   • FILTER_EXPRESSION: an expression that defines which logs you want to keep. The expression has a limit of 2,048 characters. For details, see Log filtering.

   • LOGGING_METADATA: the metadata annotations that you want to include in the logs:

     • Use include-all to include all metadata annotations.
     • Use exclude-all to exclude all metadata annotations (default).
     • Use custom to include a custom list of metadata fields that you specify in METADATA_FIELDS.

   • METADATA_FIELDS: a comma-separated list of metadata fields you want to include in the logs. For example, src_instance,dst_instance. Can be set only if LOGGING_METADATA is set to custom.

API

Enable VPC Flow Logs for an existing subnet.

PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET_NAME
{
  "logConfig": {
    "enable": true
    ...other logging fields.
  },
  "fingerprint": "SUBNETWORK_FINGERPRINT"
}

Replace the following:

• PROJECT_ID: the ID of the project where the subnet is located.
• REGION: the region where the subnet is located.
• SUBNET_NAME: the name of the existing subnet.
• SUBNET_FINGERPRINT: the fingerprint ID for the existing subnet, which is provided when you describe a subnet.
• For the other logging fields, see Enabling VPC Flow Logging when you create a subnet.

For more information, refer to the subnetworks.patch method.

Console

1. In the Google Cloud console, go to the Interconnect page.

   Go to Interconnect

2. In the VLAN attachments tab, select one or more VLAN attachments and then click menuManage flow logs in the selection bar at the top of the list.

3. In menuManage flow logs, click Add new configuration.

4. Enter a Name for the new VPC Flow Logs configuration.

5. Optional: Adjust the Aggregation interval and any of the settings in the Advanced settings section:

   • Whether to configure log filtering. By default, Keep only logs that match a filter is deselected.
   • Whether to include metadata in the final log entries. By default, Metadata annotations includes all fields.
   • The Secondary sampling rate. 100% means that all entries generated by the primary flow log sampling process are kept. The primary flow log sampling rate isn't configurable. For more information, see Log sampling and processing.

6. Click Save.

API

To create a VPC Flow Logs configuration for a VLAN attachment, use the projects.locations.vpcFlowLogsConfigs.create method.

POST https://networkmanagement.googleapis.com/v1beta1/projects/PROJECT_ID/locations/global/vpcFlowLogsConfigs
{
  "name": "CONFIG_NAME"
  "interconnectAttachment": "VLAN_ATTACHMENT"
  "description": "DESCRIPTION"
  "state": "STATE"
  "aggregationInterval": "AGGREGATION_INTERVAL",
  "flowSampling": "SAMPLE_RATE",
  "filterExpr": "FILTER_EXPRESSION",
  "metadata": "LOGGING_METADATA",
  "metadataFields": "METADATA_FIELDS"
}

Replace the following:

• PROJECT_ID: the ID of the Google Cloud project where you want to create the VPC Flow Logs configuration. Must be in the same project as the VLAN attachment.
• CONFIG_NAME: a name for the VPC Flow Logs configuration.
• VLAN_ATTACHMENT: the VLAN attachment that you want to log, in the format projects/PROJECT_ID/regions/REGION/interconnectAttachments/NAME:
  • PROJECT_ID: the ID of the Google Cloud project the VLAN attachment belongs to.
  • REGION: the region of the VLAN attachment.
  • NAME: the name of the VLAN attachment.
• DESCRIPTION: optional description of the VPC Flow Logs configuration.
• STATE: the state of the VPC Flow Logs configuration. This parameter must be set to ENABLED. If you want to pause flow logs collection, you can change the state to DISABLED after creating the configuration as described in Update configuration parameters for VLAN attachments and Cloud VPN tunnels.
• AGGREGATION_INTERVAL: the aggregation interval for flow logs generated by this configuration. The interval can be set to any of the following: INTERVAL_5_SEC (default), INTERVAL_30_SEC, INTERVAL_1_MIN, INTERVAL_5_MIN, INTERVAL_10_MIN, or INTERVAL_15_MIN.
• SAMPLE_RATE: the secondary flow sampling rate. Secondary flow sampling can be set from greater than 0.0 to 1.0 (all logs). Default is 1.0. For more information, see Log sampling and processing.
• FILTER_EXPRESSION: an expression that defines which logs you want to keep. The expression has a limit of 2,048 characters. For details, see Log filtering.
• LOGGING_METADATA: the metadata annotations that you want to include in the logs:
  • Use INCLUDE_ALL_METADATA to include all metadata annotations (default).
  • Use EXCLUDE_ALL_METADATA to exclude all metadata annotations.
  • Use CUSTOM_METADATA to include a custom list of metadata fields that you specify in METADATA_FIELDS.
• METADATA_FIELDS: a comma-separated list of metadata fields that you want to include in the logs. For example, src_instance,dst_instance. Can be set only if LOGGING_METADATA is set to CUSTOM_METADATA.

Console

1. In the Google Cloud console, go to the VPN page.

   Go to VPN

2. In the Cloud VPN tunnels tab, select one or more Cloud VPN tunnels and then click menuManage flow logs in the selection bar at the top of the list.

3. In menuManage flow logs, click Add new configuration.

4. Enter a Name for the new VPC Flow Logs configuration.

5. Optional: Adjust the Aggregation interval and any of the settings in the Advanced settings section:

   • Whether to configure log filtering. By default, Keep only logs that match a filter is deselected.
   • Whether to include metadata in the final log entries. By default, Metadata annotations includes all fields.
   • The Secondary sampling rate. 100% means that all entries generated by the primary flow log sampling process are kept. The primary flow log sampling rate isn't configurable. For more information, see Log sampling and processing.

6. Click Save.

API

To create a VPC Flow Logs configuration for a Cloud VPN tunnel, use the projects.locations.vpcFlowLogsConfigs.create method.

POST https://networkmanagement.googleapis.com/v1beta1/projects/PROJECT_ID/locations/global/vpcFlowLogsConfigs
{
  "name": "CONFIG_NAME"
  "vpnTunnel": "VPN_TUNNEL"
  "description": "DESCRIPTION"
  "state": "STATE"
  "aggregationInterval": "AGGREGATION_INTERVAL",
  "flowSampling": "SAMPLE_RATE",
  "filterExpr": "FILTER_EXPRESSION",
  "metadata": "LOGGING_METADATA",
  "metadataFields": "METADATA_FIELDS"
}

Replace the following:

• PROJECT_ID: the ID of the Google Cloud project where you want to create the VPC Flow Logs configuration. Must be in the same project as the Cloud VPN tunnel.
• CONFIG_NAME: a name for the VPC Flow Logs configuration.
• VPN_TUNNEL: the Cloud VPN tunnel that you want to log, in the format projects/PROJECT_ID/regions/REGION/vpnTunnels/NAME:
  • PROJECT_ID: the ID of the Google Cloud project project the Cloud VPN tunnel belongs to.
  • REGION: the region of the Cloud VPN tunnel.
  • NAME: the name of the Cloud VPN tunnel.
• DESCRIPTION: optional description of the VPC Flow Logs configuration.
• STATE: the state of the VPC Flow Logs configuration. This parameter must be set to ENABLED. If you want to pause flow logs collection, you can change the state to DISABLED after creating the configuration as described in Update configuration parameters for VLAN attachments and Cloud VPN tunnels.
• AGGREGATION_INTERVAL: the aggregation interval for flow logs generated by this configuration. The interval can be set to any of the following: INTERVAL_5_SEC (default), INTERVAL_30_SEC, INTERVAL_1_MIN, INTERVAL_5_MIN, INTERVAL_10_MIN, or INTERVAL_15_MIN.
• SAMPLE_RATE: the secondary flow sampling rate. Secondary flow sampling can be set from greater than 0.0 to 1.0 (all logs). Default is 1.0. For more information, see Log sampling and processing.
• FILTER_EXPRESSION: an expression that defines which logs you want to keep. The expression has a limit of 2,048 characters. For details, see Log filtering.
• LOGGING_METADATA: the metadata annotations that you want to include in the logs:
  • Use INCLUDE_ALL_METADATA to include all metadata annotations (default).
  • Use EXCLUDE_ALL_METADATA to exclude all metadata annotations.
  • Use CUSTOM_METADATA to include a custom list of metadata fields that you specify in METADATA_FIELDS.
• METADATA_FIELDS: a comma-separated list of metadata fields that you want to include in the logs. For example, src_instance,dst_instance. Can be set only if LOGGING_METADATA is set to CUSTOM_METADATA.

Console

1. In the Google Cloud console, go to the VPC networks page.

   Go to VPC networks

2. Click the VPC network where you want to view the subnets.

3. Click the Subnets tab and view the Flow logs column to see if logging is on or off.

gcloud

1. In the Google Cloud console, activate Cloud Shell.

   Activate Cloud Shell

   At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.

2. Run the following command:

   gcloud compute networks subnets list \
      --project PROJECT_ID \
      --network="NETWORK" \
      --format="csv(name,region,logConfig.enable)"

   Replace the following:

   • PROJECT_ID: the ID of the project you are querying.
   • NETWORK: the name of the network containing the subnets.

Console

In the Google Cloud console, do the following.

• To view which VLAN attachments have VPC Flow Logs enabled:

  1. Go to the Interconnect page.

     Go to Interconnect

  2. Click the VLAN attachments tab and view the Flow logs column to see if logging is on or off.

• To view which Cloud VPN tunnels have VPC Flow Logs enabled:

  1. Go to the VPN page.

     Go to VPN

  2. Click the Cloud VPN tunnels tab and view the Flow logs column to see if logging is on or off.

Console

1. In the Google Cloud console, go to the VPC Flow Logs page.

   Go to VPC Flow Logs

2. Click the Subnets, VLAN attachments, or VPN tunnels tab.

   • Subnets lists subnets that have an active VPC Flow Logs configuration.
   • VLAN attachments lists VLAN attachments for Cloud Interconnect that have active or paused VPC Flow Logs configurations.
   • VPN tunnels lists Cloud VPN tunnels that have active or paused VPC Flow Logs configurations.

API

To view VPC Flow Logs configurations, use the projects.locations.vpcFlowLogsConfigs.list and projects.locations.vpcFlowLogsConfigs.get methods.

View all VPC Flow Logs configurations.

GET https://networkmanagement.googleapis.com/v1beta1/projects/PROJECT_ID/locations/global/vpcFlowLogsConfigs

View a single VPC Flow Logs configuration.

GET https://networkmanagement.googleapis.com/v1beta1/projects/PROJECT_ID/locations/global/vpcFlowLogsConfigs/CONFIG_NAME

Replace the following:

• PROJECT_ID: the ID of the Google Cloud project that contains the VPC Flow Logs configuration or configurations that you want to view.
• CONFIG_NAME: the name of the VPC Flow Logs configuration.

Console

1. In the Google Cloud console, go to the VPC networks page.

   Go to VPC networks

2. Under Subnets in current project, click the subnet that you want to update.

3. Click Edit.

4. Optional: Adjust any of the following settings:

   • The Aggregation interval. By default, the aggregation interval is set to 5 sec.
   • Whether to configure log filtering. By default, Keep only logs that match a filter is deselected.
   • Whether to include metadata in the final log entries. By default, Metadata annotations includes all fields.
   • The Secondary sampling rate. 50% means that half of entries generated by the primary flow log sampling process are kept. The primary flow log sampling rate isn't configurable. For more information, see Log sampling and processing.

5. Click Save.

Alternatively, you can update your VPC Flow Logs configuration parameters by using the menu Manage flow logs menu under Subnets in current project on the VPC networks page.

gcloud

1. In the Google Cloud console, activate Cloud Shell.

   Activate Cloud Shell

   At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.

2. Run the following command:

   gcloud compute networks subnets update SUBNET_NAME \
      [--logging-aggregation-interval=AGGREGATION_INTERVAL] \
      [--logging-flow-sampling=SAMPLE_RATE] \
      [--logging-filter-expr=FILTER_EXPRESSION] \
      [--logging-metadata=LOGGING_METADATA] \
      [--logging-metadata-fields=METADATA_FIELDS] \
   

   Replace the following:

   • AGGREGATION_INTERVAL: the aggregation interval for flow logs in that subnet. The interval can be set to any of the following: 5-sec (default), 30-sec, 1-min, 5-min, 10-min, or 15-min.
   • SAMPLE_RATE: the secondary flow sampling rate. Secondary flow sampling can be set from 0.0 (no sampling) to 1.0 (all logs). Default is 0.5. For more information, see Log sampling and processing.
   • FILTER_EXPRESSION: an expression that defines what logs you want to keep. The expression has a limit of 2,048 characters. For details, see Log filtering.

   • LOGGING_METADATA: the metadata annotations that you want to include in the logs:

     • Use include-all to include all metadata annotations.
     • Use exclude-all to exclude all metadata annotations (default).
     • Use custom to include a custom list of metadata fields that you specify in METADATA_FIELDS.

   • METADATA_FIELDS: a comma-separated list of metadata fields you want to include in the logs. For example, src_instance,dst_instance. Can be set only if LOGGING_METADATA is set to custom.

API

Modify the log sampling fields to update VPC Flow Logs behaviors.

PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET_NAME
{
  "logConfig": {
    ...fields to modify
  },
  "fingerprint": "SUBNETWORK_FINGERPRINT"
}

Replace the following:

• PROJECT_ID: the ID of the project where the subnet is located.
• REGION: the region where the subnet is located.
• SUBNET_NAME: the name of the existing subnet.
• SUBNET_FINGERPRINT: the fingerprint ID for the existing subnet, which is provided when you describe a subnet.
• For the fields that you can modify, see Enabling VPC Flow Logging when you create a subnet.

For more information, refer to the subnetworks.patch method.

Console

1. In the Google Cloud console, go to the VPC Flow Logs page.

   Go to VPC Flow Logs

2. Select the VLAN attachments or VPN tunnels tab:

   • To update VPC Flow Logs parameters for VLAN attachments, select VLAN attachments.
   • To update VPC Flow Logs parameters for Cloud VPN tunnels, select VPN tunnels.

3. Select one or more VPC Flow Logs configurations that you want to update and click Edit.

4. Optional: Adjust any of the following:

   • The Aggregation interval. By default, the aggregation interval is set to 5 sec.
   • Whether to set the Status of the VPC Flow Logs configuration to on or off. The On status means that the selected VPC Flow Logs configuration is active and generates flow logs.
   • Whether to configure log filtering. By default, Keep only logs that match a filter is deselected.
   • Whether to include metadata in the final log entries. By default, Metadata annotations includes all fields.
   • The Secondary sampling rate. 100% means that all entries generated by the primary flow log sampling process are kept. The primary flow log sampling rate isn't configurable. For more information, see Log sampling and processing.

5. Click Save.

Alternatively, you can update your VPC Flow Logs configuration parameters by using the menu Manage flow logs menu in the VLAN attachments tab on the Interconnect page and in the VPN tunnels tab on the VPN page.

API

To modify VPC Flow Logs configuration parameters, use the projects.locations.vpcFlowLogsConfigs.patch method.

Update a VPC Flow Logs configuration for a VLAN attachment.

PATCH https://networkmanagement.googleapis.com/v1beta1/projects/PROJECT_ID/locations/global/vpcFlowLogsConfigs/CONFIG_NAME
{
  "interconnectAttachment": "VLAN_ATTACHMENT"
  ...fields to modify
}

Update a VPC Flow Logs configuration for a Cloud VPN tunnel.

PATCH https://networkmanagement.googleapis.com/v1beta1/projects/PROJECT_ID/locations/global/vpcFlowLogsConfigs/CONFIG_NAME
{
  "vpnTunnel": "VPN_TUNNEL"
  ...fields to modify
}

Replace the following:

• PROJECT_ID: the ID of the Google Cloud project that contains the VPC Flow Logs configuration.
• CONFIG_NAME: the name of the VPC Flow Logs configuration that you want to update.
• VLAN_ATTACHMENT or VPN_TUNNEL:
  • To update a VPC Flow Logs configuration for a VLAN attachment, specify the VLAN_ATTACHMENT in the format projects/PROJECT_ID/regions/REGION/interconnectAttachments/NAME.
  • To update a VPC Flow Logs configuration for a Cloud VPN tunnel, specify the VPN_TUNNEL in the format projects/PROJECT_ID/regions/REGION/vpnTunnels/NAME.
  • Replace the following:
    • PROJECT_ID: the ID of the Google Cloud project the VLAN attachment or Cloud VPN tunnel belongs to.
    • REGION: the region of the VLAN attachment or Cloud VPN tunnel.
    • NAME: the name of the VLAN attachment or Cloud VPN tunnel.

For information about the fields that you can modify, see Enable VPC Flow Logs for a VLAN attachment (Preview) or Enable VPC Flow Logs for a VPN tunnel (Preview).

Console

1. In the Google Cloud console, go to the VPC networks page.

   Go to VPC networks

2. Click the subnet that you want to update.

3. Click Edit.

4. For Flow logs, select Off.

5. Click Save.

gcloud

1. In the Google Cloud console, activate Cloud Shell.

   Activate Cloud Shell

   At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.

2. Run the following command:

   gcloud compute networks subnets update SUBNET_NAME \
      --no-enable-flow-logs
   

API

Disable VPC Flow Logs on a subnet to stop collecting log records.

PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/subnetworks/SUBNET_NAME
{
  "logConfig": {
    "enable": false
  },
  "fingerprint": "SUBNETWORK_FINGERPRINT"
}

Replace the following:

• PROJECT_ID: the ID of the project where the subnet is located.
• REGION: the region where the subnet is located.
• SUBNET_NAME: the name of the existing subnet.
• SUBNET_FINGERPRINT: the fingerprint ID for the existing subnet, which is provided when you describe a subnet.

For more information, refer to the subnetworks.patch method.

Console

1. In the Google Cloud console, go to the VPC Flow Logs page.

   Go to VPC Flow Logs

2. Select the VLAN attachments or VPN tunnels tab:

   • To turn off a VPC Flow Logs configuration for a VLAN attachment, select VLAN attachments.
   • To turn off a VPC Flow Logs configuration for a Cloud VPN tunnel, select VPN tunnels.

3. Select one or more VPC Flow Logs configurations that you want to turn off and change the configuration status to Turn off or Turn all off. The Turn all off option in the Change configuration status menu appears only if your selection includes both active and inactive VPC Flow Logs configurations.

Console

1. In the Google Cloud console, go to the VPC Flow Logs page.

   Go to VPC Flow Logs

2. Select the Subnets, VLAN attachments, or VPN tunnels tab:

   • To delete a VPC Flow Logs configuration for a subnet, select Subnets.
   • To delete a VPC Flow Logs configuration for a VLAN attachment, select VLAN attachments.
   • To delete a VPC Flow Logs configuration for a Cloud VPN tunnel, select VPN tunnels.

3. Select one or more VPC Flow Logs configurations that you want to delete and click Delete.

API

To delete a VPC Flow Logs configuration for a VLAN attachment or a Cloud VPN tunnel, use the projects.locations.vpcFlowLogsConfigs.delete method.

DELETE https://networkmanagement.googleapis.com/v1beta1/projects/PROJECT_ID/locations/global/vpcFlowLogsConfigs/CONFIG_NAME

Replace the following:

• PROJECT_ID: the ID of the Google Cloud project that contains the VPC Flow Logs configuration that you want to delete.
• CONFIG_NAME: the name of the VPC Flow Logs configuration.