Assigned
Status Update
No update yet.
Comments
ma...@google.com
ba...@google.com
ba...@google.com
ma...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
[Deleted User] <[Deleted User]>
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.
ma...@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.
Description
by digging in the log from cloud run, i am able to get the full error log but it is really hard to get the context from the google cloud reporting alone.
this is what an error looks like in error reporting. stack trace on cloud error reporting. [Tue Oct 17 2023 14:20:14 GMT+0545 (Nepal Time).png]
this is the log on gcloud logging error on logging [Tue Oct 17 2023 14:20:32 GMT+0545 (Nepal Time).png]
how to make cloud error reporting to able to collect the complete stack trace for an error?