Configuring and Using VPC Flow Logs in Cloud Logging Reviews

Alireza V. · Reviewed over 4 years ago

Kevin R. · Reviewed over 4 years ago

Maximus T. · Reviewed over 4 years ago

hans W. · Reviewed over 4 years ago

ong w. · Reviewed over 4 years ago

Andrew C. · Reviewed over 4 years ago

ong w. · Reviewed over 4 years ago

Sabeena A. · Reviewed over 4 years ago

Manisha S. · Reviewed over 4 years ago

Michael D. · Reviewed over 4 years ago

Farah D. · Reviewed over 4 years ago

PAULINE L. · Reviewed over 4 years ago

Reyna C. · Reviewed over 4 years ago

Daniel W. · Reviewed over 4 years ago

jsonPayload.dest_instance is not found in the BigQuery, maybe log format change? #standardSQL SELECT jsonPayload.dest_instance, resource FROM `flowlogs_dataset.compute_googleapis_com_vpc_flows*` WHERE jsonPayload.connection.dest_port = 22 LIMIT 1000

Lee S. · Reviewed over 4 years ago

one of the table fields was not in the table given in the instrution under task 6

Iqbal M. · Reviewed over 4 years ago

darren r. · Reviewed over 4 years ago

Challenging to get this working, may need updating with latest big query features, some more explanations on why some packet locations are russia etc would be interesting

Sean J. · Reviewed over 4 years ago

Needs update. In step 6.6 the task is to run SELECT jsonPayload.dest_instance,..... but this field does not exist.

Marcus F. · Reviewed over 4 years ago

Keshaba K. · Reviewed over 4 years ago

Tauseef Y. · Reviewed over 4 years ago

Daniel W. · Reviewed over 4 years ago

Jon O. · Reviewed over 4 years ago

Rahul M. · Reviewed over 4 years ago

vpc flow logging does not capture metadata by fedault (as of 1 March 2021) The lab therefore fails to capture information as described. Update needed .... gcloud compute networks subnets update default \ --region us-central1 --enable-flow-logs --logging-metadata=include-all gcloud compute networks subnets update default \ --region europe-west1 --enable-flow-logs --logging-metadata=include-all

MICHAEL C. · Reviewed over 4 years ago