Status Update
No update yet.
Comments
be...@google.com
Hello
Thank you for reaching out to us!
This issue seems to be outside of the scope of Issue Tracker. This Issue Tracker is a forum for end users to report bugs and request features on Google Cloud products. Please go through
I recommend you to
I'm going to close this thread which will no longer be monitored. In case you want to report a new issue, please do not hesitate to create a new Issue Tracker describing your issue.
Thank you
de...@google.com
Yes, that is correct. I will send this information to the customer as well, but from my understanding they would like the above information to be accessible through GUI in the instances page, as well as having a distinction for the types of disk usage within billing.
be...@google.com
Understood, I will be forwarding this information and requests to the appropriate teams. They will decide whether or not to approve the request, and if approved there is no ETA for these features.
Thanks again. Kind regards,
de...@google.com
Great, thanks for the update!
Description
Description of the issue:
Resource usage in App Engine Flex is not transparent. This includes persistent storage, the number of CPUs, and the amount of memory / instance type.
Where this information is currently found:
Currently, we are only able to find any reference to these resources on the App Engine page itself, under "Versions" -->"View" (on the row for the running App Engine deployment), and even then is only available in the YAML config. The table on the App Engine "Instances" page didn't include any columns exposing resource usage, which seems like something that could be improved.
Where this information should/could be found:
From Customer perspective the backing resources should be visible in the resources widget on the front dashboard and within the compute engine dashboard. Additionally (or alternatively) they should have line items that are distinct from non-App Engine Compute Engine resources in the billing dashboard.
Why this is important:
Customer recently observed a large spike in charges for persistent disks which were incurred due to a resource request in the app.yaml configuration and were not transparent to the customer. Customer believes this is a very problematic user interface defect. The billing dashboard also did not differentiate between persistent disk usage for vanilla compute engine instances and the VMs used by App Engine flexible environment, which made debugging harder.