关于“AHYBRID041 Observing Anthos Services”的评价

Sushant B. · 已于 about 1 year前审核

Abirami P. · 已于 about 1 year前审核

Patrick L. · 已于 about 1 year前审核

Ananth V. · 已于 about 1 year前审核

Joanna P. · 已于 about 1 year前审核

Arulram R. · 已于 about 1 year前审核

Kaloyan S. · 已于 about 1 year前审核

Edivan R. L. · 已于 about 1 year前审核

tung t. · 已于 about 1 year前审核

Ernesto I. · 已于 about 1 year前审核

Mariusz K. · 已于 about 1 year前审核

Tapas C. · 已于 about 1 year前审核

sanjay g. · 已于 about 1 year前审核

Lazard T. · 已于 about 1 year前审核

Ifiok N. · 已于 about 1 year前审核

Richa M. · 已于 about 1 year前审核

Sabrine B. · 已于 about 1 year前审核

Sebastian B. · 已于 about 1 year前审核

Daniel M. · 已于 about 1 year前审核

Sujit R. · 已于 about 1 year前审核

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. · 已于 about 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. · 已于 about 1 year前审核

Diego C. · 已于 about 1 year前审核

ANKITA K. · 已于 about 1 year前审核

half of lab is not working

Barry K. · 已于 about 1 year前审核