The problem you have encountered:

Cloud Run reports the Span ID as a decimal, instead of the expected HEX

  "insertId": "6635db6a000888d899991f1d",
  "httpRequest": {
    "requestMethod": "GET",
    "requestUrl": "https://foo.a.run.app/",
    "requestSize": "1219",
    "status": 503,
    "responseSize": "1021",
  },
  "resource": {
    "type": "cloud_run_revision",
    "labels": {
    }
  },
  "timestamp": "2024-05-04T06:53:27.039717Z",
  "severity": "ERROR",
  "labels": {
  "trace": "projects/foobar/traces/1bfb3d7ee8f27d2b79137152a89d8e09",
  "receiveTimestamp": "2024-05-04T06:53:30.563570954Z",
  "spanId": "8555224234567796988",
  "traceSampled": true
}

What you expected to happen:

The Span ID should be reported as a HEX ( "spanId": "76ba431d233a08fc", ) as described in the documentation (consistent with the Google HTTP Loadbalanser), see LogEntry

Steps to reproduce:

Create a Cloud Run application
Hit the public endpoint
Go to the logs and look at the produced Log Entry

Other information (workarounds you have tried, documentation consulted, etc):

LogEntry

Issue 338634230

Links (3)

Issue metadata