AHYBRID041 Observing Anthos Services Reviews

So many things were either incorrect or broken...did not get the chance to actually trace anything because of it. 1) loadgenerator deployment was not not functioning due to "Does not have minimum availability" 2) When referencing the ionstructions: "In the Google Cloud Console, on the Navigation menu, click Trace > Trace List. A trace graph displays service requests made within the demo application." - 'Trace List' does not exist and there was no graph in Trace Explorer, likely due to the loadgenerator deployment never getting off the ground. 3) Less important, but noticed the PROJECT_NUMBER value displayed was incorrect This has the potential to be highly valuable for those wanting to learn about Anthos/Istio/Envoy, but it falls short because it is not being maintatined/updated.

Jason S. · Reviewed over 1 year ago

The load generator deployment wasn't working. I'm going to give it another go but I think it was also why I wasn't able to see the latency metric alert triggered. Also after creating the SLO it wasn't being displayed under the service. But it definitely existed because attempting to re-create the SLO with the same name gave me a naming conflict.

Tyler M. · Reviewed over 1 year ago

Diego C. · Reviewed over 1 year ago

ANKITA K. · Reviewed over 1 year ago

half of lab is not working

Barry K. · Reviewed over 1 year ago

Shivanjli k. · Reviewed over 1 year ago

Santosh V. · Reviewed over 1 year ago

loadgenerator serviece was not deployed.

FRANCISCO JAVIER G. · Reviewed over 1 year ago

Joao A. · Reviewed over 1 year ago

goood

ANKIT K. · Reviewed over 1 year ago

Vishnu G. · Reviewed over 1 year ago

Vasanth Venkatesh G. · Reviewed over 1 year ago

Leszek M. · Reviewed over 1 year ago

Srinivasan V. · Reviewed over 1 year ago

Dharani A. · Reviewed over 1 year ago

Rabee A. · Reviewed over 1 year ago

Error with the loadgenerator pod init container failing. Attempt 10: Pinging frontend: frontend:80... + echo 'Attempt 10: Pinging frontend: frontend:80...' + wget --server-response http://frontend:80 + awk '/^ HTTP/{print $2}' + STATUSCODE= + '[' -eq 200 ] sh: 200: unknown operand

Joe A. · Reviewed over 1 year ago

Vinayak B. · Reviewed over 1 year ago

Muhammad Alwi A. · Reviewed over 1 year ago

P Anish R. · Reviewed over 1 year ago

Valeriy C. · Reviewed over 1 year ago

The entire lab seems half broken. The SLO is full of permission errors, some interfaces don't have anything that matches the descriptions written, the asmcli command hanged twice, traces were not being exported, the demo app was slow at all times (not just after the canary deployment), etc. Overall, the entire thing needs to be revisited.

Angelo B. · Reviewed over 1 year ago

subhasis m. · Reviewed over 1 year ago

Abhaya M. · Reviewed over 1 year ago

good one

sumit k. · Reviewed over 1 year ago