Assigned
Status Update
No update yet.
Comments
ju...@playful.software
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
dh...@google.com
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.
da...@whimsical.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.
Description
This would allow us to ingest those spans into our OpenTelemetry collector (for example using a CloudRun service consuming this topic), and then to our external services relying on OTEL (for example, Honeycomb).
More context:
Currently LoadBalancers are inserting themselves into the OTEL trace, creating a span for the load-balancer request and adjusting the OTEL headers of the backend request. This breaks cross-service traces as they change the parent span ID.
I wrote a simple logs-to-honeycomb service (
I can see the span in CloudTrace, but I have no way to export it back into our OTEL collector. The easiest way would be the proposed Cloud Trace sink to pub/sub, and then sent it to Honeycomb using a simple service similar to the one I posted above.