Next ’24 is April 9-11. Join us for three days of immersive sessions and experiences in Las Vegas. Space is limited,register now.
Gain visibility into the performance, availability, and health of your applications and infrastructure.
Get started now with:dashboards,theOps Agent for VMs,andManaged Service for Prometheus
Built on the same backend used by Google that holds over65 quadrillion points on disk
Learn how Cloud Monitoring helpscustomersimplement SRE principles to improve their businesses
Stay up-to-date with thelatest blogs and resources
Benefits
For Google Cloud and other environments
Cloud Monitoring offers automatic out-of-the-box metric collection dashboards for Google Cloud services. It also supports monitoring of hybrid and multicloud environments.
Identify trends, prevent issues
Metrics, events, and metadata are displayed with rich query language that helps identify issues and uncover patterns. Service-level objectives measure user experience and improve collaboration with developers.
Reduce monitoring overhead
One integrated service for metrics, uptime monitoring, dashboards, and alerts reduces time spent navigating between systems. Observability in context makes metrics available within Google Cloud resource pages.
Key features
Automatically infer or custom defineservice-level objectives (SLOs)for applications and get alerted when SLO violations occur. Check out ourstep-by-step guideto learn how to set SLOs, following SRE best practices.
Google Cloud’s operations suite offersManaged Service for Prometheusfor use with Kubernetes, which features self-deployed and managed collection options to simplify metrics collection, storage, and querying. For VMs, you can use theOps Agent,which combines logging and metrics collection into a single agent that can be deployed at scale using popular configuration and management tools.
Discover and monitor all Google Cloud resources and services, with no additional instrumentation, integrated right into the Google Cloud console.
Customers
What's new
Sign upfor Google Cloud newsletters to receive product updates, event information, special offers, and more.
Documentation
In this tutorial you will work directly in the Google Cloud Console to create a Compute Engine instance (VM), install the Ops Agent, and test that it is working.
Learn how to monitor a Compute Engine virtual machine (VM) instance with Cloud Monitoring.
Learn how to set up the managed collector, which is best suited for applications you are building new on GKE or refactoring.
This page describes some of the features of the Cloud Monitoring API v3.
Learn how to track overall consumption and monitor the performance of your APIs.
Get familiar with service-level indicators (SLIs) and service-level objectives (SLOs).
Create service-level objectives (SLOs) for custom and automatically detected services. Identify metrics you want to use in your service-level indicators (SLIs).
All features
Synthetic monitoring | Continuouslytrack the performanceof your web applications and APIs using automated script based tests. Monitor for faulty behavior such as regressions, broken features, high response times, and unexpected status codes. Create alerts to be notified proactively in case of unexpected behavior. |
SLO monitoring | Automatically infer or custom defineservice-level objectives (SLOs)for applications and get alerted when SLO violations occur. |
Custom metrics | Instrument your application to monitorapplication and business-level metricsvia Cloud Monitoring. |
Google Cloud Console integration | Discover and monitorall Google Cloud resources and services, with no additional configuration, integrated right into the Google Cloud console. |
Managed Service for Prometheus | Monitor and alerton your workloads, using Prometheus, without having to manually manage and operate Prometheus at scale. |
Ops Agent | Deploy theOps Agenton your Google Cloud VMs to collect detailed metrics and logs from your applications and system. Try the in-console,step-by-step tutorialto experience installing the agent on a live VM. |
Logging integration | Drill down from dashboards and charts to logs. Create, visualize, and alert onmetrics based on log data. |
Dashboards | Get visibility into your cloud resources and services with no configuration. Definecustom dashboardsand take advantage of Google’s powerful data visualization tools. |
Multiple project and group/cluster support | Createmetrics scopesto monitor single or multiple projects together, and createresource groupsto define relationships based on resource names, tags, security groups, projects, regions, accounts, and other criteria. Use those relationships to create targeted dashboards and topology-aware alerting policies. |
Alerting | Configurealerting policiesto notify you when events occur or particular system or custom metrics violate rules that you define. Use multiple conditions to define complex alerting rules. Receive notifications via email, SMS, Slack, PagerDuty, and more. |
Uptime monitoring | Monitor the availabilityof your internet-accessible URLs, VMs, APIs, and load balancers from probes around the globe with uptime checks. Create alerts to be notified proactively if there is an outage. |
Pricing
The pricing for Google Cloud Monitoring lets you control your usage and spending. You can use the free data usage allotments to get started with no upfront fees or commitments. Learn more in thepricing details guide.
Feature | Price1 | Free allotment per month | Effective date |
---|---|---|---|
All Monitoringdata except data ingested by using Managed Service for Prometheus | $0.2580/MiB1:first 150–100,000 MiB $0.1510/MiB: next 100,000–250,000 MiB$0.0610/MiB: >250,000 MiB | Allnon-chargeable Google Cloud metrics First 150 MiB per billing account formetrics charged by bytes ingested | July 1, 2018 |
Metrics ingested by usingGoogle Cloud Managed Service for Prometheus,includingGKE control plane metrics | $0.060/millionsamples†:first 0-50 billion samples ingested# $0.048/million samples: next 50-250 billion samples ingested $0.036/million samples: next 250-500 billion samples ingested $0.024/million samples: >500 billion samples ingested | Not applicable | August 8, 2023 |
Monitoring data ingested by usingGKE workload metrics | GKE workload metrics is deprecated and removed in GKE 1.24. During the deprecation period, ingestion of GKE workload metrics is not charged. | Not applicable | Not applicable |
MonitoringAPI calls | $0.01/1,000 API calls (Write API calls are free) | First 1 million API calls included per billing account | July 1, 2018 |
Execution ofMonitoring uptime checks | $0.30/1,000 executions‡ | 1 million executions per Google Cloud project | October 1, 2022 |
Execution ofsynthetic monitors | $1.20/1,000 executions* | 100 executions per billing account | November 1, 2023 |
1For pricing purposes, all units such as MB and GB representbinarymeasures. For example, 1 MB is 220bytes. 1 GB is 230bytes. These binary units are also known asmebibyte(MiB)andgibibyte(GiB).
†Google Cloud Managed Service for Prometheus uses Cloud Monitoring storage for externally created metric data and uses the Monitoring API to retrieve that data. Managed Service for Prometheus meters based on samples ingested instead of bytes to align with Prometheus' conventions. For more information about sample-based metering, seePricing for controllability and predictability.For computational examples, seePricing examples based on samples ingested.
#Samples are counted per billing account.
‡Executions are charged to the billing account in which they are defined. For more information, seePricing for uptime-check execution.
*Executions are charged to the billing account in which they are defined. For each execution, you might incur additional charges from other Google Cloud services, including services such as Cloud Functions, Cloud Storage, and Cloud Logging. For information about these additional charges, see the pricing document for the respective Google Cloud service.
Start building on Google Cloud with $300 in free credits and 20+ always free products.