Version latest

• 3.11.3 (latest)
• 3.11.0
• 3.10.0
• 3.9.0
• 3.8.0
• 3.7.0
• 3.6.0
• 3.5.0
• 3.4.0
• 3.3.1
• 3.2.5
• 3.1.2
• 3.0.0
• 2.7.2
• 2.6.0
• 2.5.0
• 2.4.0
• 2.3.1
• 2.2.0
• 2.1.1
• 2.0.2
• 1.15.3
• 1.14.0
• 1.13.0
• 1.12.1

Automatic Trace/Span ID Extraction

NOTE: All LogEntry fields populated manually will override those populated via methods referred to in this section.

The Google Cloud Logging library can automatically populate LogEntry fields trace, span_id, and trace_sampled via OpenTelemetry integration, or extracting header information from an HTTP request.

OpenTelemetry Integration

If you have the OpenTelemetry SDK package installed and are logging from within an active OpenTelemetry span, that log entry will automatically have the trace, span_id, and trace_sampled fields populated from that span. More information about OpenTelemetry can be found here.

HTTP headers

Another possible method of automatic trace / span_id is via extraction from HTTP headers. This is prioritized after OpenTelemetry and requires a supported Python web framework. Trace information is automatically populated from either the W3C Traceparent or X-Cloud-Trace-Context headers. Populating trace information this way also automatically populates the http_request field in the LogEntry as well.