Correlate Trace Spans Metrics Logging Bottlenecks

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An e-commerce backend running on Google Cloud experiences periodic latency spikes during high-traffic sales events. When inspecting distributed trace waterfalls in Cloud Trace, the DevOps team identifies an elongated span corresponding to a database query operation within the ordering service.

You need to correlate this trace span with Cloud Logging entries and Cloud Monitoring metrics to determine whether the latency spike is caused by unoptimized application query logic or infrastructure-level resource constraints.

Which diagnostic workflow should you use?

Query Cloud Logging for compute.instances.hostError audit logs and run netstat -s on the database virtual machine to monitor TCP socket buffer overruns.

Inspect the HTTP payload size in Cloud Logging using httpRequest.cacheLookup=true, and scale the Cloud SQL database tier to Large to bypass infrastructure metrics analysis.

Filter Cloud Logging by the trace identifier to inspect correlated logs, and analyze Cloud SQL Query Insights alongside Cloud Monitoring metrics to compare physical versus logical reads and memory statistics.

Configure Istio sidecar proxy injection to overwrite the traceparent context header with custom StatsD agent metrics in Cloud Monitoring.

Professional Cloud DevOps Engineer

Correlate Trace Spans Metrics Logging Bottlenecks

Related questions