Configuring an HTTP Load Balancer with Google Cloud Armor Reviews

himangshu s. · Reviewed almost 4 years ago

prateek g. · Reviewed almost 4 years ago

Danish K. · Reviewed almost 4 years ago

Pongsan S. · Reviewed almost 4 years ago

Ritika .. · Reviewed almost 4 years ago

Drew W. · Reviewed almost 4 years ago

Shagul H. · Reviewed almost 4 years ago

jkbjkkj S. · Reviewed almost 4 years ago

Bastian H. · Reviewed almost 4 years ago

Shagul H. · Reviewed almost 4 years ago

himangshu s. · Reviewed almost 4 years ago

Rambo S. · Reviewed almost 4 years ago

Monica M. · Reviewed almost 4 years ago

Chetan M. · Reviewed almost 4 years ago

Nandhakumar Y. · Reviewed almost 4 years ago

Dipali W. · Reviewed almost 4 years ago

himangshu s. · Reviewed almost 4 years ago

Ashuutosh W. · Reviewed almost 4 years ago

GODFREY M. · Reviewed almost 4 years ago

This was a very good lab, but I would give it a 4.5 instead of a 5. I did not get the Server Under Siege message, and when clicking on http-backend to view frontend location, there is no where that I could see to view total inbound traffic, or frontend location for that matter. After doing control-c, I could see there were indeed transactions. I just did not know how to monitor them.

Kimberly G. · Reviewed almost 4 years ago

Glauco C. · Reviewed almost 4 years ago

Had trouble generating enough traffic with siege to get significant load balancing

Rich B. · Reviewed almost 4 years ago

siege not working

Gabriela C. · Reviewed almost 4 years ago

Steps are so confusing not properly defined

Nishanth S. · Reviewed almost 4 years ago

Andrew S. · Reviewed almost 4 years ago