关于“Configuring an HTTP Load Balancer with Google Cloud Armor”的评价

Erike S. · 已于 over 6 years前审核

Conor B. · 已于 over 6 years前审核

Erike S. · 已于 over 6 years前审核

Vineet D. · 已于 over 6 years前审核

Fabian D. · 已于 over 6 years前审核

Andreas O. · 已于 over 6 years前审核

Riccardo C. · 已于 over 6 years前审核

Maurizio M. · 已于 over 6 years前审核

YING Y. · 已于 over 6 years前审核

Marco D. · 已于 over 6 years前审核

* Every time i do any stress test related lab, something fails. This time, the siege library segfaulted in the end. I wasn't able to see the load moving. * The webserver in the instance group shows a "client ip" when you open the LB ip, this is not the client ip, but apparently the proxy ip. It changes within each request I do (from the browser or from the vm-siege). this lead me to believe the vm-siege would never be really blocked. after waiting like 10 minutes it happened. it's better to leave that ip out of the output of the web server if it's not showing the real information. * the logs of the load balancer took simply too long. even after 20 minutes of the first request, i never saw an entry under the load balancer logs.

Andras G. · 已于 over 6 years前审核

Task 1 create the health check firewall rules Step 4, tcp specify all ports, "all" does not work you have to specify port range or rule will fail to create. When creating the load balancer No logs were generated in last step

Jerrell M. · 已于 over 6 years前审核

Marco R. · 已于 over 6 years前审核

Chiara N. · 已于 over 6 years前审核

Diego M. · 已于 over 6 years前审核

John Dominic F. · 已于 over 6 years前审核

Vincenzo M. · 已于 over 6 years前审核

Nick P. · 已于 over 6 years前审核

Kumar A. · 已于 over 6 years前审核

Seige is not working getting error: Error in `siege': free(): invalid size: 0x0000561ce83e2390

shraddha g. · 已于 over 6 years前审核

Unable to view logs from cloud armor

Piergiuseppe P. · 已于 over 6 years前审核

Davide P. · 已于 over 6 years前审核

Sukanya R. · 已于 over 6 years前审核

Mythili V. · 已于 over 6 years前审核

John Dominic F. · 已于 over 6 years前审核