Cloud Run is logging the Span ID as a base^10 instead of HEX in LogEntry [338634230]

Assigned

Bug

Status Update

No update yet.

Description

al...@gmail.com

created issue #1

May 4, 2024 07:08AM

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

Comments

al...@collibra.com <al...@collibra.com> #2May 5, 2024 08:53AM

I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.

Screenshot 2024-05-05 at 10.50.05.png

98 KB

View

Download

va...@google.com <va...@google.com> May 6, 2024 06:39AM

Assigned to va...@google.com.

va...@google.com <va...@google.com> May 8, 2024 06:21AM

Status: New

al...@gmail.com <al...@gmail.com> #3May 8, 2024 06:25AM

Hello! Sorry to bring up this issue after almost a year but I wanted to add that we have chosen metric identifier as

agent.googleapis.com/memory/percent_used but autoscaling didnt work out for us either. It would be appraciated if you can guide us.

ba...@google.com <ba...@google.com> #4May 14, 2024 08:35AM

Assigned to gc...@google.com.

Hi, at the moment we are using the cpu_utilization/target_utilization attribute (in app.yaml) for autoscaling in the app engine flexible environment, however it would be great if we can have the way to mention the memory_utilization metrics as well to decide on the auto scaling. It will give us more control of the auto scaling the instances than now.