Opinie (Configuring and Using VPC Flow Logs in Cloud Logging)

Nathan W. · Sprawdzono ponad 6 lat temu

Wesley d. · Sprawdzono ponad 6 lat temu

Matt C. · Sprawdzono ponad 6 lat temu

Jeffrey S. · Sprawdzono ponad 6 lat temu

Chen S. · Sprawdzono ponad 6 lat temu

William m. · Sprawdzono ponad 6 lat temu

Jeffrey S. · Sprawdzono ponad 6 lat temu

Hung T. · Sprawdzono ponad 6 lat temu

Bret R. · Sprawdzono ponad 6 lat temu

Starting up the shell takes forever.

Charlie T. · Sprawdzono ponad 6 lat temu

the vpc_flow logs took almost 30 min to show up, maybe add a note that it can take more than a few minutes for the logs to show up

Aditi C. · Sprawdzono ponad 6 lat temu

Shawn L. · Sprawdzono ponad 6 lat temu

Nikhil R. · Sprawdzono ponad 6 lat temu

Kunal Kumar G. · Sprawdzono ponad 6 lat temu

In Task 6 my BigQuery table was named compute_googleapis_com_vpc_flows_20191007 rather than compute_googleapis_com_vpc_flows as indicated in the instructions.

Jason H. · Sprawdzono ponad 6 lat temu

The first two commands to create US/EU machines failed because they already existed. It took over 10 minutes to wait for VPC flow logs to show up. Following the instructions to export the VPC flow logs to BigQuery didn't work out of the box. The rows showed up when viewing the export but when viewing the flowlogs_dataset, I don't see tables and the given sql fails.

Haddon K. · Sprawdzono ponad 6 lat temu

Edward Y. · Sprawdzono ponad 6 lat temu

Irene S. · Sprawdzono ponad 6 lat temu

Francisco G. · Sprawdzono ponad 6 lat temu

Rafael D. · Sprawdzono ponad 6 lat temu

Jay J. · Sprawdzono ponad 6 lat temu

Kim Jee F. · Sprawdzono ponad 6 lat temu

Matteo P. · Sprawdzono ponad 6 lat temu

Lab has out-of-date material. For example, the "top two lines" are different. I could never see Pub/Sub show up in Exports. Also, the last progress checker did not work, even though I successfully ran a BQ against the flow data.

Cristopher R. · Sprawdzono ponad 6 lat temu

Konrad S. · Sprawdzono ponad 6 lat temu