[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["# Monitor your usage of Sensitive Data Protection\n\nThis page describes how to use Cloud Monitoring to view and graph metrics\ndata about your Sensitive Data Protection usage.\n\nSensitive Data Protection sends detailed telemetry about your Sensitive Data Protection\nusage to Monitoring. This can be useful to monitor for\nunexpected findings, amount of data scanned or transformed, errors in\n[job triggers or jobs](/sensitive-data-protection/docs/concepts-job-triggers), and [expenses](/sensitive-data-protection/pricing).\n\nView Sensitive Data Protection metrics in Monitoring\n----------------------------------------------------\n\nUsing [Metrics Explorer](/monitoring/charts/metrics-explorer) in\nCloud Monitoring, you can dig into available metrics data to give you\ninsight into your Sensitive Data Protection usage. Monitoring\nsupports a wide variety of metrics, which you can combine with filters and\naggregations for new and insightful views.\n\nTo view the metrics for a monitored resource by using the\nMetrics Explorer, do the following:\n\n1. In the Google Cloud console, go to the\n *leaderboard* **Metrics explorer** page:\n\n [Go to **Metrics explorer**](https://console.cloud.google.com/monitoring/metrics-explorer)\n\n \u003cbr /\u003e\n\n If you use the search bar to find this page, then select the result whose subheading is\n **Monitoring**.\n2. In the **Metric** element, expand the **Select a metric** menu, and then select a resource type and metric type. For example, to chart the CPU utilization of a virtual machine, do the following:\n 1. (Optional) To reduce the menu's options, enter part of the metric name in the **Filter bar** . For this example, enter `utilization`.\n 2. In the **Active resources** menu, select **VM instance**.\n 3. In the **Active metric categories** menu, select **Instance**.\n 4. In the **Active metrics** menu, select **CPU utilization** and then click **Apply**.\n3. To filter which time series are displayed, use the\n [**Filter** element](/monitoring/charts/metrics-selector#filter-option).\n\n4. To combine time series, use the menus on the\n [**Aggregation** element](/monitoring/charts/metrics-selector#select_display).\n For example, to display the CPU utilization for your VMs, based on their zone, set the\n first menu to **Mean** and the second menu to **zone**.\n\n All time series are displayed when the first menu of the **Aggregation** element\n is set to **Unaggregated** . The default settings for the **Aggregation** element\n are determined by the metric type you selected.\n\nTo see Sensitive Data Protection-specific metrics in Metrics Explorer, search with\n`dlp.googleapis.com` to refine your search results.\n\nTo see API metrics in Metrics Explorer, select **Consumed API** as the resource\ntype, and then use the filter and aggregation options to refine your data.\n\nAfter you've found the metrics you want, you can use Monitoring\nto create custom dashboards and alerts that will help you continue to monitor\nand maintain a robust application.\n\nGraph the metrics\n-----------------\n\nYou can graph metrics by aggregating them using\nAdvanced Aggregation. Use the following settings:\n\n- Aligner: SUM\n- Alignment Period: 1440\n\n[](/static/sensitive-data-protection/docs/images/stackdriver-metric.png) Cloud Monitoring metric configuration (click to enlarge).\n\nYou get a chart showing the results per day.\n[](/static/sensitive-data-protection/docs/images/stackdriver-chart.png) Cloud Monitoring metric configuration (click to enlarge).\n\nCloud Monitoring supports alerting on all metrics. Using the\nSensitive Data Protection metrics, you can alert on use cases that include:\n\n- Monitor `content_bytes_inspected_count` or `content_bytes_transformed_count` to alert when spend has exceeded budget for a day.\n- Alert when the number of total findings or findings for a specific infoType exceed a threshold. For example, you can build an alert if `CREDIT_CARD_NUMBER` findings exceed 0 in a given project where no PII should exist.\n\nAvailable metrics\n-----------------\n\nThe following metric type names must be prefixed with\n`dlp.googleapis.com/`. That prefix has been omitted from the entries in the\ntable."]]