AHYBRID041 Como observar serviços do Anthos avaliações

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. · Revisado há over 1 year

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. · Revisado há over 1 year

Diego C. · Revisado há over 1 year

ANKITA K. · Revisado há over 1 year

half of lab is not working

Barry K. · Revisado há over 1 year

Shivanjli k. · Revisado há over 1 year

Santosh V. · Revisado há over 1 year

loadgenerator serviece was not deployed.

FRANCISCO JAVIER G. · Revisado há over 1 year

Joao A. · Revisado há over 1 year

goood

ANKIT K. · Revisado há over 1 year

Vishnu G. · Revisado há over 1 year

Vasanth Venkatesh G. · Revisado há over 1 year

Leszek M. · Revisado há over 1 year

Srinivasan V. · Revisado há over 1 year

Dharani A. · Revisado há over 1 year

Rabee A. · Revisado há over 1 year

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. · Revisado há over 1 year

Vinayak B. · Revisado há over 1 year

Muhammad Alwi A. · Revisado há over 1 year

P Anish R. · Revisado há over 1 year

Valeriy C. · Revisado há over 1 year

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. · Revisado há over 1 year

subhasis m. · Revisado há over 1 year

Abhaya M. · Revisado há over 1 year

good one

sumit k. · Revisado há over 1 year