Monitoring Google Cloud

eG Enterprise offers a specialized Google Cloud model for monitoring a Google Cloud project that manages the cloud services offered by Google.

Figure 1 : Layer model of the Google Cloud component

Each layer that is part of this model is mapped to tests that pull a variety of metrics revealing the composition, health, and monthly cost of instances and services in the target project. Using these metrics, administrators can find quick and accurate answers for the following performance queries:

  • Is the cloud available? If so, how quickly is it responding to the requests?
  • Is any Filestore instance in erratic/suspened state currently?
  • Is any Filestore instance slow in processing read and write operations?
  • Which storage bucket received maximum number of API call requests?
  • How many times a user/service account was authenticated using each storage bucket?
  • Which storage bucket was slow in receiving data from and/or sending data to external applications and users?
  • What is the current status of each VM hosted on the Google Cloud?
  • Which VM instance over-utilized the memory/CPU/disk resources over the period of time?
  • Which VM instance dropped maximum number of packets during transmission/reception?
  • How many VMs are currently in powered on/powered off state?
  • Is any BigTable instance in unknown state?
  • Which BigTable instance utilized maximum percentage of storage?
  • How many requests to a table in each BigTable instance failed (if any)?
  • What is the current status of each Spanner instance?
  • Is any SQL instance utilizing storage space excessively? If so, which one is it?
  • Is any SQL instance in deleted/unknown/suspened/failed state?
  • What is the availability status of each SQL instance?

  • Is backup configuration is enabled for a SQL instance?

  • How well each SQL instance utilized CPU/memory/disk resources?

  • Is any SQL instance slow in receiving and/or sending data?

  • What is the rate at which each SQL instance processed the network traffic?

  • How many slots are being used by the BigQuery project to process the queries?

  • What is the average time take by the BigQuery project to execute the queries successfully?

  • Is any composer instance in error state currently?
  • What is the CPU/memory/disk utilization of each composer instance?
  • Is the airflow database in each composer instance healthy?