Assigned
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
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
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.
[Deleted User] <[Deleted User]>
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.
ma...@google.com
Hi, I do not see any memory metrics in neither console nor stackdriver. Is this connected to this issue?
Description
In async flows, Spans are often linked together, instead of a parent-child relationship, navigating between these Spans/Traces is currently cumbersome, as the Link is only surfaced unidirectionally (from CONSUMER to PRODUCER, but not vice versa).
How this might work:
I would expect linked Spans to be surfaced bi-directionally to help with quickly navigating from the PRODUCER to all of the CONSUMERs (or from upstream to downstream). In the analysis tool, this could be surfaced as a separate group under "Span Links"
If applicable, reasons why alternative solutions are not sufficient:
There is no alternative, currently filtering does not allow surfacing Traces by links either, so the only way is to know where to look and to manually find the downstream Trace/Span.
Other information (workarounds you have tried, documentation consulted, etc):
- Filtering by linked Span ID
- Fetching data from the API to build something on top of the data, but same issue, no filtering available