Correlate Trace Context Structured Logs Cloud Run Compute Engine

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.

Your organization runs a microservices architecture distributed across Cloud Run and Compute Engine instances. During incident investigations, engineers struggle to correlate application logs with distributed traces in Google Cloud Observability.

You need to implement end-to-end trace context propagation between services and ensure application log entries are automatically correlated with Cloud Trace in Cloud Logging.

Which configuration should you implement?

Propagate trace context across HTTP calls using standard trace context headers (such as W3C traceparent or X-Cloud-Trace-Context), and emit structured JSON logs containing the logging.googleapis.com/trace field formatted as projects/[PROJECT_ID]/traces/[TRACE_ID] and the logging.googleapis.com/spanId field.

Configure VPC Flow Logs on all subnets, route logs to Cloud Storage, and use Google Security Operations UDM mapping tables to join connection IP tuples with application execution logs.

Embed trace identifiers into the HTTP User-Agent string of internal requests and rely on unstructured plaintext logs ingested via the Cloud Logging agent without metadata enrichment.

Add an X-Goog-Request-Reason HTTP header containing the trace ID to all internal service requests, and format logs by writing the trace identifier exclusively inside jsonPayload.message.

Professional Cloud DevOps Engineer

Correlate Trace Context Structured Logs Cloud Run Compute Engine

Related questions