Como monitorar aplicativos no Google Cloud avaliações

Devanshu S. · Revisado há over 3 years

Sebastian E. · Revisado há over 3 years

Suchitra S. · Revisado há over 3 years

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. · Revisado há over 3 years

Ashish V. · Revisado há over 3 years

MADHUR J. · Revisado há over 3 years

Krystian W. · Revisado há over 3 years

gpgpc

Anil Chandra K. · Revisado há over 3 years

Raj S. · Revisado há over 3 years

Shubham R. · Revisado há over 3 years

vipul c. · Revisado há over 3 years

AHAM A. · Revisado há over 3 years

Anil Chandra K. · Revisado há over 3 years

Sumeth N. · Revisado há over 3 years

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

Praveen P. · Revisado há over 3 years

Jacek S. · Revisado há over 3 years

Anil G. · Revisado há over 3 years

Shridhar B. · Revisado há over 3 years

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. · Revisado há over 3 years

Gayatri M. · Revisado há over 3 years

Victor Manuel M. · Revisado há over 3 years

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. · Revisado há over 3 years

err

Ashish K. · Revisado há over 3 years

total shit

LAWRENCE E. · Revisado há over 3 years

Kamil N. · Revisado há over 3 years