Cloud Run does not include "service.name" attributes on the OpenTelemetry spans it sends to Cloud Trace [325741116]

Assigned

Bug

Status Update

No update yet.

Description

ja...@pinian.co

created issue #1

Feb 18, 2024 07:21PM

When tracing with Open Telemetry, the "

service.name" span attribute is treated specially in the Cloud Trace Explorer, and given its own column, so you can easily see which part of the distributed system the span is from.

Cloud Run does not report its own service name correctly.

The two attachments show the difference in Cloud Trace.

Repro:

1. Create a service that sends Open Telemetry spans to Cloud Trace.
2. Deploy the service through Cloud Run.
3. Make a request to the service.

Outcome: The Service column in Cloud Trace is empty for spans sent from Cloud Run.

Expected: The Service column says "Cloud Run".

Screenshot 2024-02-18 at 2.16.49 PM.png

162 KB

View

Download

Screenshot 2024-02-18 at 2.16.28 PM.png

120 KB

View

Download

Comments

va...@google.com <va...@google.com> Feb 19, 2024 06:33AM

Assigned to va...@google.com.

dh...@google.com <dh...@google.com> Feb 19, 2024 10:40AM

Reassigned to dh...@google.com.

dh...@google.com <dh...@google.com> #2Feb 19, 2024 12:59PM

Reassigned to gc...@google.com.

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

ma...@bonniernews.se <ma...@bonniernews.se> #3Sep 20, 2024 12:28PM

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.

ka...@askelephant.ai <ka...@askelephant.ai> #4Feb 17, 2025 05:31AM

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.

Issue 325741116