Configuring and Using VPC Flow Logs in Cloud Logging Reviews

Luis T. · Reviewed 20 days ago

Melissa K. · Reviewed 20 days ago

Tony P. · Reviewed 20 days ago

Melissa K. · Reviewed 20 days ago

Tuấn L. · Reviewed 20 days ago

MANIMARAN N. · Reviewed 21 days ago

mairim y. · Reviewed 21 days ago

Boddu L. · Reviewed 21 days ago

Nasurudeen Z. · Reviewed 21 days ago

Yasir I. · Reviewed 21 days ago

Francesco V. · Reviewed 21 days ago

Ihor S. · Reviewed 21 days ago

Amarnadh K. · Reviewed 22 days ago

Amarnadh K. · Reviewed 22 days ago

Catherine M. · Reviewed 22 days ago

Monica Yadira S. · Reviewed 22 days ago

Himanshu G. · Reviewed 22 days ago

Abhishek-Purushottam S. · Reviewed 22 days ago

The logs were not under port 22. They were under port 443 for me. Not sure if anything should change here, but a copied query for port 22 will continuously yield no results.

Kirsten B. · Reviewed 23 days ago

Tomas Marx-Raacz v. · Reviewed 23 days ago

lab OK-ish, however while creating Log Sink, a message as below appeared: Sink successfully created. However, we were unable to grant correct permissions to the destination. Please complete the operation by manually granting the sink's service account service-433043662026@gcp-sa-logging.iam.gserviceaccount.com permission to write logs to the destination, bigquery.googleapis.com/projects/qwiklabs-gcp-01-32a83d8f73c5/datasets/flowlogs_dataset. Logs will not be written to this destination until the service account has correct permissions. the student user didn't have resourcemanager.projects.setIamPolicy permissions so couldn't add permissions to service account. investigating logs, severity: "ERROR" textPayload: "Cloud Logging sink configuration error in qwiklabs-gcp-01-32a83d8f73c5, sink FlowLogBQExport: dataset_permission_denied ()" However, deleting and recreating the sink helped solve the problem and complete the lab. I guess a race condition against "very fresh" dataset may have occurred and permissions were missing?

Jakub R. · Reviewed 23 days ago

Real work

Kingsley D. · Reviewed 23 days ago

first lab was buggy and ssh didn't work. had to restart and try again

Tonia B. · Reviewed 23 days ago

Kobus M. · Reviewed 23 days ago

Hanna N. · Reviewed 23 days ago