search

jmac11 / googlecloudsql

Automatically exported from code.google.com/p/googlecloudsql
0 stars 0 forks source link

Enable Load Monitoring #110

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
This is a feature/enhancement request.

Currently users are responsible for picking an instance size for our Cloud SQL 
instance, but we have no way of knowing if our instance is undersized or 
oversized because there are no CPU or RAM usage statistics provided.

We can see the following on the instance overview tab, but none of that tells 
us if we should have a larger or smaller instance running.

Storage Usage (GB)
Number of Read/Write operations
Egress Bytes
Active Connections
MySQL Queries
MySQL Questions
InnoDB Pages Read/Written (pages/sec)
InnoDB Data fsyncs (operations/sec)
InnoDB Log fsyncs (operations/sec) 

You should add CPU uptime and RAM usage stats so that we can size our instances 
accordingly.

Thank you,
Cavan

Original issue reported on code.google.com by cavanmor...@softcoil.com on 9 May 2015 at 11:08

GoogleCodeExporter commented 9 years ago 
I have forwarded this request to the engineering team. We will update this 
issue with any progress updates and a resolution.

Best regards, Vaqar

Original comment by vshe...@google.com on 14 May 2015 at 5:14