AHYBRID041 Observing Anthos Services Reviews

no indication of progress

Adrián G. · Reviewed yaklaşık 1 yıl ago

The loadgenerator service was not running and I failed when trying to start it manually.

Jan G. · Reviewed yaklaşık 1 yıl ago

Its confusing that Anthos is in the middle of moving to Kubernetes Enterprise, making it hard to find as you can't search for Anthos in the menu. Also 'Trace List' was nowhere to be found.

Rasmus B. · Reviewed yaklaşık 1 yıl ago

Sushant B. · Reviewed yaklaşık 1 yıl ago

Abirami P. · Reviewed yaklaşık 1 yıl ago

Patrick L. · Reviewed yaklaşık 1 yıl ago

Ananth V. · Reviewed yaklaşık 1 yıl ago

Joanna P. · Reviewed yaklaşık 1 yıl ago

Arulram R. · Reviewed yaklaşık 1 yıl ago

Kaloyan S. · Reviewed yaklaşık 1 yıl ago

Edivan R. L. · Reviewed yaklaşık 1 yıl ago

tung t. · Reviewed yaklaşık 1 yıl ago

Ernesto I. · Reviewed yaklaşık 1 yıl ago

Mariusz K. · Reviewed yaklaşık 1 yıl ago

Tapas C. · Reviewed yaklaşık 1 yıl ago

sanjay g. · Reviewed yaklaşık 1 yıl ago

Lazard T. · Reviewed yaklaşık 1 yıl ago

Ifiok N. · Reviewed yaklaşık 1 yıl ago

Richa M. · Reviewed yaklaşık 1 yıl ago

Sabrine B. · Reviewed yaklaşık 1 yıl ago

Sebastian B. · Reviewed yaklaşık 1 yıl ago

Daniel M. · Reviewed yaklaşık 1 yıl ago

Sujit R. · Reviewed yaklaşık 1 yıl ago

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 1 yıldan fazla 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 1 yıldan fazla ago