Stackdriver: Qwik Start avaliações

useful :)

Maria Jesus A. · Revisado há about 8 years

ok...the lab seemed to have problems and run slow.

Matthew A. · Revisado há about 8 years

Jorge S. · Revisado há about 8 years

Javier S. · Revisado há about 8 years

Samit B. · Revisado há about 8 years

Jeff P. · Revisado há about 8 years

Marcin S. · Revisado há about 8 years

not able to restart apache2; submit defect not able to much of the lab.

Jeff P. · Revisado há about 8 years

zakaria b. · Revisado há about 8 years

Umer A. · Revisado há about 8 years

Arkadiusz G. · Revisado há about 8 years

R M. · Revisado há about 8 years

Priyanka J. · Revisado há about 8 years

gopalakrishnan s. · Revisado há about 8 years

Thomas V. · Revisado há about 8 years

Kyle B. · Revisado há about 8 years

DeAngelo R. · Revisado há about 8 years

Christopher C. · Revisado há about 8 years

Great Lab

Sarma A. · Revisado há about 8 years

satisfait

Mezieche T. · Revisado há about 8 years

Muhammad F. · Revisado há about 8 years

Comment 1: In the step “Add Apache2 HTTP Server to your instance”, the first sentence says:” If you were to browse to the instance's external IP address, you'd get an error”. As the quest “Baseline:Infrastructure” is presented as “This Quest of all-Introductory-level Self-Paced Labs (…) intended for the complete beginner in Google Cloud”, I feel that a one-sentence explanation explaining why we would get an error would be welcome for complete beginners in Google Cloud like me. Comment 2: In the instruction "If you visit http://[external IP]", adding a few words to say that it is to be found in the Console would be helpful. I was looking for the information in the Strackdriver command interface to find the external IP because the last actions took place in this window. As I am not used to play with different windows, I lost some time reading in the lines of code. Even one line of instruction to ask practitioners to write down the external IP address after creation of the instance would make everything easy-breezy. Overall, very interesting lab with a meaningful display of some basic capabilities to create an uptime check / an alerting policy. Just a bit more information here and there (see comments) and it would be a great lab, in my opinion. Comment 3: For the first occurrence of SSH, state it in full before using the abbreviation. Comment 4:

Laurent N. · Revisado há about 8 years

Steven G. · Revisado há about 8 years

Jeetinder S. · Revisado há about 8 years

Sarish A. · Revisado há about 8 years