Configuring and Using VPC Flow Logs in Cloud Logging Reviews

Jonathan J. · Reviewed about 7 years ago

Pankaj S. O. · Reviewed about 7 years ago

Gaurav M. · Reviewed about 7 years ago

Dinh T. · Reviewed about 7 years ago

Roman O. · Reviewed about 7 years ago

Roman O. · Reviewed about 7 years ago

Kalpika R. · Reviewed about 7 years ago

Very nice lab

Anil Kumar K. · Reviewed about 7 years ago

Scott B. · Reviewed about 7 years ago

Andrey L. · Reviewed about 7 years ago

Alexandros T. · Reviewed about 7 years ago

Alessandro D. · Reviewed about 7 years ago

Pankaj S. O. · Reviewed about 7 years ago

Isaac R. · Reviewed about 7 years ago

Some steps had to be completed guessing

Danny B. · Reviewed about 7 years ago

Pankaj S. O. · Reviewed about 7 years ago

Predrag T. · Reviewed about 7 years ago

In the 2nd last step. there was a query about port 22 traffic logs. the logs weren't being created because the sink wasn't created for the big query. If possible add a step for that as well.

Awais A. · Reviewed about 7 years ago

Abhishek G. · Reviewed about 7 years ago

Garrett S. · Reviewed about 7 years ago

not sure if it's a bug, or just a lag. when disabling VPC flow (last step before clean up step), I re-enter the command* and clicked refresh before the flow logs were off. *"gcloud compute networks subnets update default \ --region europe-west1 --no-enable-flow-logs"

LTI S. · Reviewed about 7 years ago

Please review this step: Add the following line to the end of the filter. Replace Internal_IP_Of_default_us_vm with the internal IP address of your default_us_vm instance (you recorded this earlier) Reason: We did not create an instance "default_us_vm". We created an instance "default-us-vm". (underline <-> hyphen)

Sascha B. · Reviewed about 7 years ago

Zach B. · Reviewed about 7 years ago

PARAMESH K. · Reviewed about 7 years ago

Robert M. · Reviewed about 7 years ago