Level Up Conference logo
Level Up Conference June 24-26th, Austin, Texas
Register Now

Best Practices

Monitoring Google Cloud Costs: Three Tips for Maximizing your Investment


Posted by Sarah Terry, Product Manager at LogicMonitor
Jan 8, 2019

Whether you are just migrating to Google Cloud Platform (GCP) or have well-established workloads running, monitoring spend is essential to maximizing your investment. As of a recent release, you can monitor GCP spend alongside resource performance with LogicMonitor. Monitoring GCP spend can help you better understand how cloud usage impacts costs and when that usage needs to be optimized to meet a budget. The following are three tips for monitoring costs that will help you maximize your GCP investment:

  1. Don’t just look once a month

Pay-as-you-go billing models and per-second rates enable you to quickly impact overall spend by adjusting usage, but checking your bill once a month won’t provide you with enough time or flexibility to do so. Monitor your GCP spend on a more regular basis (e.g. daily) to identify when usage causes a jump in costs and course correct if needed. You may even consider setting alert thresholds such that you receive a notification when spend increases quickly, or beyond your desired budget. For example, a developer may spin up a few Cloud SQL instances with a large amount of CPU and memory resources just to test something specific, and forget to shut them down afterward. If you wait for your bill at the end of the month, you’ll see the cost for the forgotten instances, but it’ll be too late to do anything about it. In contrast, monitoring of daily spend will clearly show the increase.


A graph displaying GCP total spend in LogicMonitor
  1. Make it actionable

Monitoring total spend over time will provide you with an indication of when costs increase more quickly than they should, but won’t help you narrow down the cause. Make sure your monitored spend is presented meaningfully to ensure it’s both tangible and actionable. By default, LogicMonitor breaks down monitored GCP spend by project, services, and operations. This granularity can help you pinpoint what is behind specific cost increases, and how you can help. With the previous example involving forgotten Cloud SQL instances, you’d want to see the increase in spend for the Cloud SQL service, and even for the operations specific to the machine types used. This level of detail makes it easiest to identify the cause.

A graph displaying GCP spend by service in LogicMonitor



  1. Monitor cost alongside performance

Monitoring cost alone can help you identify abnormalities in spend, but won’t help you identify normal trends in spend that can be optimized. Monitoring performance and utilization alongside cost can help you identify over-provisioned resources, and where spend that is trending normally can be reduced. For example, you may look at Compute Engine instances by lowest CPU usage, and identify that instances can be shut down all together to save money.

A LogicMonitor graph displaying the ten GCP Compute Engine Instances with the lowest CPU Usage over time


In summary, you can maximize your GCP investment by monitoring spend more frequently than once a month, ensuring that monitored spend is meaningful and actionable, and looking at performance and utilization to identify additional costs that can be optimized.


Want to see the above dashboard for your GCP environment? Sign up for LogicMonitor today and download the dashboard here

Let's get started.

Get a 14-day free trial, no CC required.

Sign Up Free explore platform