Assigned
Status Update
Comments
am...@renault.com <am...@renault.com> #2
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
sc...@mediamarktsaturn.com <sc...@mediamarktsaturn.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.
cy...@renault.com <cy...@renault.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.
ba...@google.com <ba...@google.com> #5
Hi, I do not see any memory metrics in neither console nor stackdriver. Is this connected to this issue?
sc...@mediamarktsaturn.com <sc...@mediamarktsaturn.com> #6
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
ba...@google.com <ba...@google.com> #7
Hi ,
Can somebody tell the exact metric for memory based autoscaling
Can somebody tell the exact metric for memory based autoscaling
sc...@mediamarktsaturn.com <sc...@mediamarktsaturn.com> #8
Hello,
ok than thank you for explaining it to me.
Thx
ok than thank you for explaining it to me.
Thx
ka...@softchoice.com <ka...@softchoice.com> #9
Hi Team,
Any update on this feature request? Understood that this was logged as a bug but looking for some feedback as to why it was changed and line of sight into any ETA on resolution.
+1
Thanks!
Any update on this feature request? Understood that this was logged as a bug but looking for some feedback as to why it was changed and line of sight into any ETA on resolution.
+1
Thanks!
ra...@dlpcapital.com <ra...@dlpcapital.com> #10
Replying to this email means your email address will be shared with the
team that works on this product.
On Wed, Apr 24, 2024 at 2:31 PM <buganizer-system@google.com> wrote:
team that works on this product.
On Wed, Apr 24, 2024 at 2:31 PM <buganizer-system@google.com> wrote:
--
[image: DLP Capital+] <
Ravinder Kamal
Database Administrator/Architect
Office Phone: (470) 704-8450
ravinder.kamal@dlpcapital.com
DLP Capital | DLPCapital.com <
[image: linkedin icon] <
twitter icon] <
<
<
<
An *Inc. 5000* Fastest Growing Company 11 years in a row.
Claim your copy
<
of *Building an Elite Organization*, an Amazon,
USA Today, & WSJ Best Selling Book.
Claim your copy
<
of
*Building an Elite Career.*
[image: DP Capital Events] <
DISCLAIMER: The information contained in this message is proprietary and/or confidential and may be privileged. If you are not the intended recipient of this communication, you are hereby notified to: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately by replying to this email message or by telephone.
Description
Problem you have encountered:
Metric
bigquery.googleapis.com/storage/stored_bytes
sometimes doesn’t have a value.Apparently, the metric does not reflect real data sometimes with a high amount of entries between projects.
What you expected to happen:
The data should be reflected correctly in all cases.
Other information:
A workaround for this issue would be to use the table
TABLE_STORAGE_TIMELINE
if the information that needs to be gathered can be located within a project. To gather data for more projects at once, the tableTABLE_STORAGE_TIMELINE_BY_ORGANIZATION
should be used instead.The following documentation is helpful to understand the workaround.