Reporting & Monitoring Overview

It's important to review your Google Maps Platform API usage, quota, and billing information on a regular basis. This information helps you measure API usage, stay within predefined consumption limits, and control costs through planned budgets. Reviewing this information can also alert you to any unexpected interactions that might occur between your applications and the Google Maps Platform services.

The Maps Platform provides two tools that can help you review usage, quota, and billing information:

  • Reporting: A set of predefined visual reports that let you easily see basic API usage, quota, and billing information in the Google Cloud Console. You can quickly determine the number of API calls, see how close you are to hitting API usage quotas, and monitor billing usage over time.
  • Monitoring: A set of tools, both in the Cloud Console and through an API, that let you monitor API usage, quota, and billing information and define alerts when any of these metrics approaches a predefined limit.

    Monitoring lets you create your own customized monitoring dashboards displaying your metrics as different chart types. You can also issue alert notifications, such as emails or SMS text messages, when a metric crosses a predefined threshold.


Reporting in the Maps Platform provides a set of predefined visual reports that let you easily see basic API usage, quota, and billing information in the Cloud Console. View reports for your Maps Platform API usage, quota, and billing numbers by using the Cloud Console.

APIs & Services reports

The Cloud Console APIs & Services report provides usage metrics for all APIs enabled for your project, including the Maps Platform APIs and SDKs as well as all other Google APIs and services.

This image shows the APIs & Services report.

A screenshot of the Monitoring APIs page in the Google Cloud Console, displaying the APIs & Services
  report dashboard. It shows separate charts for Traffic, Errors, and Median Latency. These charts
  can show data for one hour up through 30 days.


Quotas set limits on the number of requests your project can make to the Maps Platform APIs. Requests can be limited in three ways:

  • Per day
  • Per minute
  • Per user per minute (where available)

Only successful requests and requests that cause server errors count against quota. Requests that fail authentication do not count against quota.

Quota usage is displayed in graphs on the Quotas report page in the Cloud Console.

Screenshot of the Maps' Quotas page in the Google Cloud Console. It shows quotas by API using
  a selector, then shows Map Loads relative to the set quotas for the API in question.


The Cloud Console Billing reports provide billing and related cost information for the project you have selected.

The Cloud Billing Reports page lets you view your Google Cloud Platform usage costs for all projects linked to a Cloud Billing account. To help you view the cost trends that are important to you, you can select a data range, specify a time range, configure the chart filters, and group by project, service, SKU, or location.

Cloud Billing reports can help you answer questions like these:

  • How is my current month's Google Cloud Platform spending trending?
  • What project cost the most last month?
  • What are my forecasted future costs based on historical trends?
  • How much am I spending by region?

This image shows the Billing report.

Screenshot of the Maps' Billing page in the Google Cloud Console. It shows billing information
  for one calendar month for all projects.


Cloud Monitoring collects measurements of your service and of the Google Cloud Platform resources that you use. For example, you can monitor API calls or quota usage over a specified time interval.

Not only can you define custom metrics and charts, but you can also define alerts. Use alerts to send a notification when the performance of a service doesn't meet criteria you define. For example, you can send a notification as an email, text message, to the Cloud Console Mobile App, and other options.


In Cloud Monitoring:

  • A metric describes something that is measured. Examples of metrics include the number of calls to an API, percent of a usage quota consumed, or a virtual machine's CPU utilization.
  • A time series is a data structure that contains time-stamped measurements of a metric and information about the source and meaning of those measurements.

To explore metric data, build a chart with Metrics Explorer. For example, to view the request count of an API in one minute intervals for the past hour, use Metrics Explorer to construct a chart that displays the most recent data.

Screenshot of a custom line chart showing API counts. The chart can show data from one hour
  to six weeks, or a customized time frame.


Dashboards let you view and monitor your time-series data as a collection of charts. To create custom dashboards, you can use the Cloud Console or the Cloud Monitoring API.

The following image shows a custom dashboard with two charts: a quota chart on the left, and an API count chart on the right.

A screenshot of a custom dashboard, displaying two charts. The chart on the left is a quota chart,
  while the chart on the right is a chart of API usage. Both charts list time points on their
  horizontal axis.


To be notified when the performance of a service doesn't meet criteria you define, create an alerting policy. For example, you can create an alerting policy that notifies your on-call team when the 90th percentile of the latency of HTTP 200 responses from your service exceeds 100 ms.

Alerting gives timely awareness to problems in your cloud applications so you can resolve the problems quickly.

Cloud Monitoring supports many types of alerts such as:

  • Metric threshold alerts: Trigger an alert if a metric rises above or falls below a value for a specific duration or a metric increases or decreases by a predefined percentage.
  • Budget alerts: Trigger notifications when your costs exceed a percentage of your budget.
  • Quota alerts: Trigger notifications when your usage approaches a quota limit.

What's next