Monitoring Applications in Google Cloud avis

Devanshu S. · Examiné il y a plus de 3 ans

Sebastian E. · Examiné il y a plus de 3 ans

Suchitra S. · Examiné il y a plus de 3 ans

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. · Examiné il y a plus de 3 ans

Ashish V. · Examiné il y a plus de 3 ans

MADHUR J. · Examiné il y a plus de 3 ans

Krystian W. · Examiné il y a plus de 3 ans

gpgpc

Anil Chandra K. · Examiné il y a plus de 3 ans

Raj S. · Examiné il y a plus de 3 ans

Shubham R. · Examiné il y a plus de 3 ans

vipul c. · Examiné il y a plus de 3 ans

AHAM A. · Examiné il y a plus de 3 ans

Anil Chandra K. · Examiné il y a plus de 3 ans

Sumeth N. · Examiné il y a plus de 3 ans

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

Praveen P. · Examiné il y a plus de 3 ans

Jacek S. · Examiné il y a plus de 3 ans

Anil G. · Examiné il y a plus de 3 ans

Shridhar B. · Examiné il y a plus de 3 ans

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. · Examiné il y a plus de 3 ans

Gayatri M. · Examiné il y a plus de 3 ans

Victor Manuel M. · Examiné il y a plus de 3 ans

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. · Examiné il y a plus de 3 ans

err

Ashish K. · Examiné il y a plus de 3 ans

total shit

LAWRENCE E. · Examiné il y a plus de 3 ans

Kamil N. · Examiné il y a plus de 3 ans