Creating and Alerting on Logs-based Metrics Reviews

Eric W. · Reviewed over 1 year ago

Juan Alviandi Susanto C. · Reviewed over 1 year ago

M. Rizky Aulia Hrp C. · Reviewed over 1 year ago

Nurul Aini Komarudin C. · Reviewed over 1 year ago

Dirzy Adam C. · Reviewed over 1 year ago

Bruno T. · Reviewed over 1 year ago

Héctor Sebastián T. · Reviewed over 1 year ago

Karina E. · Reviewed over 1 year ago

Eric W. · Reviewed over 1 year ago

task 2 number 7 not similar it said "couldnt connect to server. thats why i cant complete last task

Muhammad N. · Reviewed over 1 year ago

Rizq Rahid Khairullah C. · Reviewed over 1 year ago

shalini c. · Reviewed over 1 year ago

Rizq Rahid Khairullah C. · Reviewed over 1 year ago

worst lab ever. Full of mistakes. I couldnt pull the image from GCR, image failed to load . worst lab ever. I would give negative infinity if I could

Jaana M. · Reviewed over 1 year ago

Pydipati H. · Reviewed over 1 year ago

Muhammad Rizky Fauzan Wibowo C. · Reviewed over 1 year ago

The deployment on Kubernetes doesn't work. The Pod is in ImagePullBackoff Warning Failed 12s (x2 over 65s) kubelet Failed to pull image "gcr.io/ops-demo-330920/flask_telemetry:61a2a7aabc7077ef474eb24f4b69faeab47deed9": failed to pull and unpack image "gcr.io/ops-demo-330920/flask_telemetry:61a2a7aabc7077ef474eb24f4b69faeab47deed9": failed to resolve reference "gcr.io/ops-demo-330920/flask_telemetry:61a2a7aabc7077ef474eb24f4b69faeab47deed9": unexpected status from HEAD request to https://gcr.io/v2/ops-demo-330920/flask_telemetry/manifests/61a2a7aabc7077ef474eb24f4b69faeab47deed9: 412 Precondition Failed

Antoine B. · Reviewed over 1 year ago

Dirzy Adam C. · Reviewed over 1 year ago

keigo u. · Reviewed over 1 year ago

Patrick Vicky Andrews M. · Reviewed over 1 year ago

anjg

Muqtada Hasby A. · Reviewed over 1 year ago