Assigned
Status Update
No update yet.
Comments
y....@dr-ubie.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
di...@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.
di...@google.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.
y....@dr-ubie.com
Hi, I do not see any memory metrics in neither console nor stackdriver. Is this connected to this issue?
Description
What you would like to accomplish:
We really want to have Stackdriver Trace support to CloudSQL.
We are using Stackdriver Trace in SpringBoot (2.0.5.RELEASE), CloudSQL(Postgresql), spring-cloud-gcp-starter-trace(1.0.0.RC1)
The attached file is the result of Stackdriver Trace. We have no idea how long does it take to execute the query unless we explicitly add a log statement. It's impossible to show the trace log if we use different thread/coroutine since Stackdriver Trace did not attach the trace id to the log in different thread.
How this might work:
If CloudSQL supports tracing queries, execution time, etc, we don't even need to send the huge DEBUG log that Spring creates. Also, we can use different thread to access CloudSQL.
If applicable, reasons why alternative solutions are not sufficient:
Other information (workarounds you have tried, documentation consulted, etc):