Assigned
Status Update
Comments
na...@google.com <na...@google.com> #2
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
ca...@mercari.com <ca...@mercari.com> #3
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.
ta...@google.com <ta...@google.com>
ta...@google.com <ta...@google.com>
fe...@google.com <fe...@google.com>
fe...@google.com <fe...@google.com> #4
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
Problem you have encountered:
It is unclear what is being "measured" by the heap flamegraph.
In
What you expected to happen:
In the stackdriver profiler be able to:
- select which type of heap profile type to display; whether usage or allocations
- when I select heap usage, the metrics shown (in the tooltips displayed when hovering) should make it clear that this is an instantaneous measurement
- when I select heap allocations, the metrics shown should make it clear that this is a rate of allocation (e.g. bytes/s or obj/s).
- when I read the documentation, I am able to quickly figure out what kind of profiling type I need to troubleshoot specific issues, and I get clear, consistent and actionable steps to use the profiler to that end
Steps to reproduce:
Open the heap profile, notice that only one option is available
Open the heap profiler documentation, notice that they are unclear and inconsistent
Other information (workarounds you have tried, documentation consulted, etc):