Stackdriver: Qwik Start Reviews

useful :)

Maria Jesus A. · Reviewed about 8 years ago

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

Matthew A. · Reviewed about 8 years ago

Jorge S. · Reviewed about 8 years ago

Javier S. · Reviewed about 8 years ago

Samit B. · Reviewed about 8 years ago

Jeff P. · Reviewed about 8 years ago

Marcin S. · Reviewed about 8 years ago

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

Jeff P. · Reviewed about 8 years ago

zakaria b. · Reviewed about 8 years ago

Umer A. · Reviewed about 8 years ago

Arkadiusz G. · Reviewed about 8 years ago

R M. · Reviewed about 8 years ago

Priyanka J. · Reviewed about 8 years ago

gopalakrishnan s. · Reviewed about 8 years ago

Thomas V. · Reviewed about 8 years ago

Kyle B. · Reviewed about 8 years ago

DeAngelo R. · Reviewed about 8 years ago

Christopher C. · Reviewed about 8 years ago

Great Lab

Sarma A. · Reviewed about 8 years ago

satisfait

Mezieche T. · Reviewed about 8 years ago

Muhammad F. · Reviewed about 8 years ago

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. · Reviewed about 8 years ago

Steven G. · Reviewed about 8 years ago

Jeetinder S. · Reviewed about 8 years ago

Sarish A. · Reviewed about 8 years ago