You have enabled HTTP(S) load balancing for your application, and your application developers have reported that HTTP(S) requests are not being distributed correctly to your Compute Engine Virtual Machine instances.
You want to find data about how the request are being distributed.
Which two methods can accomplish this? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.AD.
The scenario in this question assumes that you have enabled HTTP(S) load balancing for your application, but the requests are not being distributed correctly to your Compute Engine Virtual Machine instances. To troubleshoot this issue, you want to find data about how the requests are being distributed. There are several methods you can use to accomplish this, and two of them are mentioned in the answers.
A. On the Load Balancer details page of the GCP Console, click on the Monitoring tab, select your backend service, and look at the graphs. This method involves accessing the Monitoring tab on the Load Balancer details page in the GCP Console. From there, you can select your backend service and view the graphs that provide information about how the requests are being distributed. The graphs can show you data such as the number of requests per backend, the request latency, and the response codes. This method is a good way to get an overview of how the load balancer is performing.
D. In Stackdriver Monitoring, select Resources > Google Cloud Load Balancers and review the Key Metrics graphs in the dashboard. This method involves accessing the Google Cloud Load Balancers dashboard in Stackdriver Monitoring. From there, you can review the Key Metrics graphs, which provide detailed information about the load balancer's performance. The graphs can show you data such as the request rate, the response rate, the backend utilization, and the error rate. This method is useful if you need more detailed information about the load balancer's performance.
B, C, and E are not the best methods for troubleshooting this issue, as they do not provide direct information about how the requests are being distributed. However, they may be useful for other types of troubleshooting.
B. In Stackdriver Error Reporting, look for any unacknowledged errors for the Cloud Load Balancers service. This method involves accessing Stackdriver Error Reporting and looking for any unacknowledged errors related to the Cloud Load Balancers service. While this method can be useful for identifying errors in the load balancer, it does not provide information about how the requests are being distributed.
C. In Stackdriver Monitoring, select Resources > Metrics Explorer and search for https/request_bytes_count metric. This method involves accessing Metrics Explorer in Stackdriver Monitoring and searching for the https/request_bytes_count metric. While this metric can be useful for monitoring the amount of data being transmitted over HTTPS, it does not provide information about how the requests are being distributed.
E. In Stackdriver Monitoring, create a new dashboard and track the https/backend_request_count metric for the load balancer. This method involves creating a new dashboard in Stackdriver Monitoring and tracking the https/backend_request_count metric for the load balancer. While this metric can be useful for monitoring the number of requests being sent to the backend, it does not provide information about how the requests are being distributed.