Assigned
Status Update
No update yet.
Comments
va...@google.com
ba...@google.com
ba...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
sa...@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.
sa...@google.com
kk...@google.com
kk...@google.com
sh...@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.
gu...@gmail.com
Hi, I do not see any memory metrics in neither console nor stackdriver. Is this connected to this issue?
mz...@google.com
Hello Google team, I was directed to this issue by the support team when we raised concerns around the non availability of memory metrics for Auto Scaling. Is this feature 'released' or in roadmap or not considered ? Please provide some details around this
an...@google.com
Hi ,
Can somebody tell the exact metric for memory based autoscaling
Can somebody tell the exact metric for memory based autoscaling
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:Currently as per the help center article, the Maximum number of notifications is 20 a day for each log-based alert.
What you expected to happen:Option to increase the "Maximum number of notifications " quota to be more than 20 per day for each log-based alert.
Steps to reproduce:
Other information (workarounds you have tried, documentation consulted, etc):