Cloud Debugger has updated the configuration file naming and keywords that you use to block access to sensitive data
Share
Services
## Change
Cloud Debugger has updated the configuration file naming and keywords that you use to block access to sensitive data. For the updated configuration, see [Hiding sensitive data](https://cloud.google.com/debugger/docs/sensitive-data).
## Feature
Cloud Monitoring is introducing [metrics scopes](https://cloud.google.com/monitoring/settings#concept-scope). For a Google Cloud project, its metrics scope defines the projects whose metrics the project can view and monitor:
* When you create a project, its metrics scope is set to self.
* You can modify a project's metrics scope to include other Google Cloud projects, or to include AWS accounts. For more information, see [Viewing metrics for multiple projects](https://cloud.google.com/monitoring/settings/multiple-projects).
* A Google Cloud project can be included in multiple metrics scopes.
For more information about metrics scopes, see [Configuring your project for Cloud Monitoring](https://cloud.google.com/monitoring/settings).
## Change
The replacement of Cloud Monitoring Workspaces with [metrics scopes](https://cloud.google.com/monitoring/settings#concept-scope) is complete.
All of your existing Cloud Monitoring Workspaces have been migrated to the new data model.
* To access the metrics for a Google Cloud project, select that project in the Console project picker and then access the Monitoring page.
* To determine the projects whose metrics the current project can view, see [Determining visibility of metrics](https://cloud.google.com/monitoring/settings#visibility).
* For information about metrics scopes, see [Configuring your project for Cloud Monitoring](https://cloud.google.com/monitoring/settings).