[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-08-26 (世界標準時間)。"],[[["\u003cp\u003eRegularly review your Google Maps Platform API usage, quota, and billing information to control costs and identify unexpected application interactions.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Maps Platform provides Reporting and Monitoring tools to help you track and manage your API usage.\u003c/p\u003e\n"],["\u003cp\u003eReporting offers predefined visual reports in the Cloud Console for basic usage, quota, and billing insights.\u003c/p\u003e\n"],["\u003cp\u003eMonitoring provides customizable dashboards and alerts for in-depth tracking and proactive notifications.\u003c/p\u003e\n"],["\u003cp\u003eUse these tools to understand your API usage patterns, stay within quota limits, and optimize your spending.\u003c/p\u003e\n"]]],["Regularly review your Google Maps Platform API usage, quota, and billing to manage costs and detect unexpected activity. Utilize two main tools: Reporting and Monitoring. Reporting offers visual reports in the Cloud console to track API calls, quota limits, and billing. Monitoring provides tools to track these metrics, create custom dashboards, and set up alerts for predefined thresholds via various notification methods, including emails and SMS. Key actions include using Cloud console to track APIs and Billing, setting quotas, and setting metric, budget, and quota alerts.\n"],null,["It's important to review your Google Maps Platform API usage, quota, and\nbilling information on a regular basis. This information helps you\nmeasure API usage, stay within predefined consumption limits, and control costs\nthrough planned budgets. Reviewing this information can also alert you to any unexpected\ninteractions that might occur between your applications and the\nGoogle Maps Platform services.\n\nThe Maps Platform provides two tools that can help you review\nusage, quota, and billing information:\n\n- [Reporting](/maps/reporting-and-monitoring/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.\n- [Monitoring](/maps/reporting-and-monitoring/monitoring):\n A set of tools, both in the Cloud console and through an API, that let you monitor API\n usage, quota, and billing information and define alerts when any of these\n metrics approaches a predefined limit.\n\n Monitoring lets you create your own customized\n monitoring dashboards displaying your metrics as different chart types. You can also\n issue alert notifications, such as emails or SMS text messages, when a metric\n crosses a predefined threshold.\n\nReporting\n\n[Reporting](/maps/reporting-and-monitoring/reporting)\nin the Maps Platform provides a set of predefined visual reports\nthat let you easily see basic API usage, quota, and billing information in the\nCloud console. View reports for your\nMaps Platform API usage, quota, and billing numbers by using the\n[Cloud console](https://console.cloud.google.com).\n\nAPIs \\& Services reports\n\nThe Cloud console [APIs \\& Services](https://console.cloud.google.com/project/_/apis/dashboard) report\nprovides usage metrics for all APIs enabled for your project, including the\nMaps Platform APIs and SDKs as well as all other Google APIs and\nservices.\n\nThis image shows the **APIs \\& Services** report.\n\nQuotas\n\nQuotas set limits on the number of requests your project can make to the\nMaps Platform APIs. Requests can be limited in three ways:\n\n- Per day\n- Per minute\n- Per user per minute (where available)\n\nOnly successful requests and requests\nthat cause server errors count against quota. Requests that fail authentication\ndo not count against quota.\n\nQuota usage is displayed in graphs on the **Quotas** report\npage in the Cloud console.\n\nBilling\n\nThe Cloud console [Billing](https://console.cloud.google.com/project/_/billing)\nreports provide billing and related cost information for the project you have selected.\n\nThe Cloud Billing Reports page lets you view your Google Cloud usage costs\nfor all projects linked to a Cloud Billing account. To help you view the cost\ntrends that are important to you, you can select a data range, specify a time\nrange, configure the chart filters, and group by project, service, SKU, or\nlocation.\n\nCloud Billing reports can help you answer questions like these:\n\n- How is my current month's Google Cloud spending trending?\n- What project cost the most last month?\n- What are my forecasted future costs based on historical trends?\n- How much am I spending by region?\n\nThis image shows the **Billing** report.\n\nMonitoring\n\n[Cloud Monitoring](/maps/reporting-and-monitoring/monitoring)\ncollects measurements of your service and of the Google Cloud resources\nthat you use. For example, you can monitor API calls or quota usage over a\nspecified time interval.\n\nNot only can you define custom metrics and charts, but you can also define\nalerts. Use alerts to send a notification when the performance of a service\ndoesn't meet criteria you define. For example, you can send a notification as an\nemail, text message, to the Cloud console Mobile App, and other\noptions.\n\nMetrics\n\nIn Cloud Monitoring:\n\n- 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.\n- 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.\n\nTo explore metric data, build a chart with Metrics Explorer. For example,\nto view the request count of an API in one minute intervals for the past hour, use\nMetrics Explorer to construct a chart that displays the most recent data.\n\nDashboards\n\n[Dashboards](https://cloud.google.com/monitoring/dashboards) let\nyou view and monitor your time-series data as a collection of charts. To create\ncustom dashboards, you can use the Cloud console or the\nCloud Monitoring API.\n\nThe following image shows a custom dashboard with two charts:\na quota chart on the left, and an API count chart on the right.\n\nAlerts\n\nTo be notified when the performance of a service doesn't meet criteria you\ndefine, create an alerting policy. For example, you can create an alerting\npolicy that notifies your on-call team when the 90th percentile of the latency\nof HTTP 200 responses from your service exceeds 100 ms.\n\nAlerting gives timely awareness to problems in your cloud applications so you\ncan resolve the problems quickly.\n\nCloud Monitoring supports many types of alerts such as:\n\n- [Metric threshold alerts](https://cloud.google.com/monitoring/alerts/types-of-conditions#metric-threshold): 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.\n- [Budget alerts](https://cloud.google.com/billing/docs/how-to/budgets): Trigger notifications when your costs exceed a percentage of your budget.\n- [Quota alerts](https://cloud.google.com/monitoring/alerts/using-quota-metrics): Trigger notifications when your usage approaches a quota limit.\n\nWhat's next\n\n- [Reporting](/maps/reporting-and-monitoring/reporting)\n- [Monitoring](/maps/reporting-and-monitoring/monitoring)"]]
