Cloud Run Trace - support for alternative open telemetry backends [347732149]

Assigned

Feature Request

Status Update

No update yet.

Description

do...@ionq.co

created issue #1

Jun 17, 2024 11:25PM

Hi,

By default Cloud Run participates in trace propagation and even creates a Cloud Trace

https://cloud.google.com/trace/docs/trace-context#gc-context-propagation which can be very useful, but when mixed with alternative open telemetry backends in the application logic, can lead to those backends reporting missing Spans.

Would it be possible to support alternative open telemetry backends via configuration like OTEL_EXPORTER_OTLP_ENDPOINT or to support disabling the trace entirely?

Comments

va...@google.com <va...@google.com> Jun 18, 2024 06:18AM

Assigned to va...@google.com.

va...@google.com <va...@google.com> Jun 18, 2024 03:00PM

Status: New

ba...@google.com <ba...@google.com> Jun 19, 2024 05:37AM

Assigned to ma...@google.com.

ma...@google.com <ma...@google.com> #2Jun 19, 2024 09:00AM

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

ma...@google.com <ma...@google.com> Jun 19, 2024 10:32AM

Reassigned to gc...@google.com.

al...@google.com <al...@google.com> Sep 26, 2024 08:28AM

Reassigned to gc...@google.com.

en...@ingka.ikea.com <en...@ingka.ikea.com> #3Dec 13, 2024 02:36PM

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.