Memantau Aplikasi di Google Cloud Ulasan

Pranav P. · Diulas hampir 3 tahun lalu

ds

Suchitra S. · Diulas hampir 3 tahun lalu

Jacky C. · Diulas hampir 3 tahun lalu

Devanshu S. · Diulas hampir 3 tahun lalu

Sebastian E. · Diulas hampir 3 tahun lalu

Suchitra S. · Diulas hampir 3 tahun lalu

The instructions do not reflect what google's legacy screen is doing. By default it does not show legacy which this lab is based on. In Task 6.3 "When you are asked to create an alerting policy" do so.. But you are not asked and the Uptime check is just created. This is the last step of the lab. I have tried many times, ie deleted Uptime check and tried to recreate, but instructions do no match current google screens. This lab needs to be reviewed and fully updated

Jason P. · Diulas hampir 3 tahun lalu

Ashish V. · Diulas hampir 3 tahun lalu

MADHUR J. · Diulas hampir 3 tahun lalu

Krystian W. · Diulas hampir 3 tahun lalu

gpgpc

Anil Chandra K. · Diulas hampir 3 tahun lalu

Raj S. · Diulas hampir 3 tahun lalu

Shubham R. · Diulas hampir 3 tahun lalu

vipul c. · Diulas hampir 3 tahun lalu

AHAM A. · Diulas hampir 3 tahun lalu

Anil Chandra K. · Diulas hampir 3 tahun lalu

Sumeth N. · Diulas hampir 3 tahun lalu

Not Satisfied - Instructions are not clear and facing issue with google cloud profiler import

Praveen P. · Diulas hampir 3 tahun lalu

Jacek S. · Diulas hampir 3 tahun lalu

Anil G. · Diulas hampir 3 tahun lalu

Shridhar B. · Diulas hampir 3 tahun lalu

Not bad, but the instructions no longer match the UI behavior in a few different areas so I had to deviate a bit from the instruction ordering. Not a big deal but I got a stern warning about that from another lab so now I am worried about my account getting locked.

Gary C. · Diulas hampir 3 tahun lalu

Gayatri M. · Diulas hampir 3 tahun lalu

Victor Manuel M. · Diulas hampir 3 tahun lalu

Creating an app engine would not work properly via the cloud shell, I had to do it via the console. ERROR: (gcloud.app.create) HttpError accessing <https://appengine.googleapis.com/v1/apps?alt=json>: response: <{'vary': 'Origin, X-Origin, Referer', 'content-type': 'application/json; charset=UTF-8', 'date': 'Sat, 25 Mar 2023 17:25:59 GMT', 'server': 'ESF', 'cache-control': 'private', 'x-xss-protection': '0', 'x-frame-options': 'SAMEORIGIN', 'x-content-type-options': 'nosniff', 'transfer-encoding': 'chunked', 'status': '500', 'content-length': '109', '-content-encoding': 'gzip'}>, content <{ "error": { "code": 500, "message": "Internal error encountered.", "status": "INTERNAL" } } > This may be due to network connectivity issues. Please check your network settings, and the status of the service you are trying to reach. When I tried to create again, it said app engine was already running. When I tried to deploy, it said there was no app engine. In the console there was no app engine, so I created one there, and then deployed in cloud shell. Luckily I was able to finish the lab. FIX THIS for future students please.

LAWRENCE E. · Diulas hampir 3 tahun lalu