Opinie (AHYBRID041 Observing Anthos Services)

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. · Sprawdzono ponad rok temu

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. · Sprawdzono ponad rok temu

Diego C. · Sprawdzono ponad rok temu

ANKITA K. · Sprawdzono ponad rok temu

half of lab is not working

Barry K. · Sprawdzono ponad rok temu

Shivanjli k. · Sprawdzono ponad rok temu

Santosh V. · Sprawdzono ponad rok temu

loadgenerator serviece was not deployed.

FRANCISCO JAVIER G. · Sprawdzono ponad rok temu

Joao A. · Sprawdzono ponad rok temu

goood

ANKIT K. · Sprawdzono ponad rok temu

Vishnu G. · Sprawdzono ponad rok temu

Vasanth Venkatesh G. · Sprawdzono ponad rok temu

Leszek M. · Sprawdzono ponad rok temu

Srinivasan V. · Sprawdzono ponad rok temu

Dharani A. · Sprawdzono ponad rok temu

Rabee A. · Sprawdzono ponad rok temu

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. · Sprawdzono ponad rok temu

Vinayak B. · Sprawdzono ponad rok temu

Muhammad Alwi A. · Sprawdzono ponad rok temu

P Anish R. · Sprawdzono ponad rok temu

Valeriy C. · Sprawdzono ponad rok temu

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. · Sprawdzono ponad rok temu

subhasis m. · Sprawdzono ponad rok temu

Abhaya M. · Sprawdzono ponad rok temu

good one

sumit k. · Sprawdzono ponad rok temu