Google Cloud でのアプリケーションのモニタリング のレビュー

Sen Devanshu · 3年以上前にレビュー済み

Eschner Sebastian · 3年以上前にレビュー済み

Sunki Suchitra · 3年以上前にレビュー済み

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

Parr Jason · 3年以上前にレビュー済み

V. Wath Ashish · 3年以上前にレビュー済み

JAJODIA MADHUR · 3年以上前にレビュー済み

Woźniak Krystian · 3年以上前にレビュー済み

gpgpc

Karnewar Anil Chandra · 3年以上前にレビュー済み

Sharma Raj · 3年以上前にレビュー済み

Ramkisan VHOLGADE Shubham · 3年以上前にレビュー済み

chhabra vipul · 3年以上前にレビュー済み

ANDREW AHAM · 3年以上前にレビュー済み

Karnewar Anil Chandra · 3年以上前にレビュー済み

Naverattanawittaya Sumeth · 3年以上前にレビュー済み

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

Parmar Praveen · 3年以上前にレビュー済み

Signin Jacek · 3年以上前にレビュー済み

Gogia Anil · 3年以上前にレビュー済み

Balasaheb KADAM Shridhar · 3年以上前にレビュー済み

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.

Cowan Gary · 3年以上前にレビュー済み

Matole Gayatri · 3年以上前にレビュー済み

Medina Ochoa Victor Manuel · 3年以上前にレビュー済み

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.

E MCARDLE LAWRENCE · 3年以上前にレビュー済み

err

Krishna Ashish · 3年以上前にレビュー済み

total shit

E MCARDLE LAWRENCE · 3年以上前にレビュー済み

Nowak Kamil · 3年以上前にレビュー済み