Como monitorar e registrar com o Google Cloud Observability: laboratório com desafio avaliações

Muhammad Reihan Alfarizi C. · Revisado há over 1 year

Bhandit t. · Revisado há over 1 year

Alif Bayu A. · Revisado há over 1 year

Feni Mutia C. · Revisado há over 1 year

Finodya Yahdun C. · Revisado há over 1 year

SUDHEER KUMAR K. · Revisado há over 1 year

Hasan Nur Rasyid C. · Revisado há over 1 year

Nisrina Azka Salsabila C. · Revisado há over 1 year

Muhammad Fattah Ziidan C. · Revisado há over 1 year

Raoul E. · Revisado há over 1 year

Naufal Nazhif A. · Revisado há over 1 year

Muhammad R. · Revisado há over 1 year

Muhammad Fauzan Fadillah C. · Revisado há over 1 year

Amirul Mabruri C. · Revisado há over 1 year

Sirisha B. · Revisado há over 1 year

Muhammad F. · Revisado há over 1 year

Lira Serli Selviana C. · Revisado há over 1 year

Dio Adista L. · Revisado há over 1 year

Dwita Avrilly C. · Revisado há over 1 year

Dieka Septiani Safitri C. · Revisado há over 1 year

Amirul Mabruri C. · Revisado há over 1 year

Reynaldo O. · Revisado há over 1 year

Amirul Mabruri C. · Revisado há over 1 year

Marifah C. · Revisado há over 1 year

Good lab, though it seems that some resources take a bit of time to be updated in the console such as the Media_Dashboard and the input_queue_size metric after rerunning the startup script. I think that explicit notes within the lab to denote the possible wait times would do well to prevent any confusion of "missing" resources.

Feru Pratama Kartajaya C. · Revisado há over 1 year