Serverless Data Processing with Dataflow - Monitoring, Logging and Error Reporting for Dataflow Jobs Reviews

Rock P. · Reviewed over 4 years ago

Sumbono S. · Reviewed over 4 years ago

shawn r. · Reviewed over 4 years ago

Jimmy L. · Reviewed over 4 years ago

Invalid BigQuery check failed

Duy H. · Reviewed over 4 years ago

Hello, There is an error somewhere in this lab . It is impossible to validate the second step where it is requested to click on the error link in the diognistic tab ( dataflow job log) and because of that I couldn't validate the Lab.

Oussama H. · Reviewed over 4 years ago

Abanob F. · Reviewed over 4 years ago

Progress check not working

Tsz Kin L. · Reviewed over 4 years ago

Gabriel A. · Reviewed over 4 years ago

Mashu S. · Reviewed over 4 years ago

David R. · Reviewed over 4 years ago

This lab is failing the third validation step.

Mario R. · Reviewed over 4 years ago

Onur B. · Reviewed over 4 years ago

Juliano L. · Reviewed over 4 years ago

broken monitor

Randi-Michelle C. · Reviewed over 4 years ago

Jimmy L. · Reviewed over 4 years ago

Task 3 does not seem to be completing successfully for me. The requirement is to simply open the link in the dataflow error message under the diagnostics tab. I believe this is not working because the intentional invalid name bugquery-public-data.crypto_bitcoin.transactions in the lab gives me the error “permission denied” instead of “dataset not found”.

Jeremy D. · Reviewed over 4 years ago

Jimmy L. · Reviewed over 4 years ago

Duggirala V. · Reviewed over 4 years ago

Vladimir U. · Reviewed over 4 years ago

Aymen N. · Reviewed over 4 years ago

Your lab is broken, it is not adding the points even after completing the tasks.

Yash G. · Reviewed over 4 years ago

doesn't work

Meng Oon L. · Reviewed over 4 years ago

This step does not update score in task "Invalid Bigquery table": "When you click on the Diagnostics tab, you will see a clickable link. Click on it and this takes you to the Error Reporting page. This shows us an expanded view of the error. Looking at the stack trace, you will see the issue: a typo in the pipeline code"

Antonio M. · Reviewed over 4 years ago

Antoni Vicent S. · Reviewed over 4 years ago