{"id":33177,"date":"2021-01-19T11:53:29","date_gmt":"2021-01-19T11:53:29","guid":{"rendered":"https:\/\/www.testpreptraining.com\/tutorial\/?page_id=33177"},"modified":"2021-01-19T11:53:30","modified_gmt":"2021-01-19T11:53:30","slug":"provisioning-stackdriver-workspaces","status":"publish","type":"page","link":"https:\/\/www.testpreptraining.ai\/tutorial\/provisioning-stackdriver-workspaces\/","title":{"rendered":"Provisioning Stackdriver workspaces"},"content":{"rendered":"\n

Go back to GCP Tutorials<\/a><\/strong><\/p>\n\n\n\n

In this tutorial we will learn and understand about Provisioning Stackdriver workspaces.<\/p>\n\n\n\n

However, Cloud Monitoring uses Workspaces to organize monitoring information. Where a Workspace is a tool for monitoring resources in one or more Google Cloud projects or AWS accounts. A Workspace accesses metric data from its monitored projects, but the metric data remains in those projects.<\/p>\n\n\n\n

Host projects<\/strong><\/h4>\n\n\n\n

Every Workspace has a host project. The host project is the Google Cloud project for creating the Workspace. The name of the Workspace is set to the name of the host project. This isn’t configurable.<\/p>\n\n\n\n

However, the host project for Workspace stores all of the configuration content for dashboards, alerting policies, uptime checks, notification channels, and group definitions that you configure. If you delete the host project, you also delete the Workspace.<\/p>\n\n\n\n

\"Google<\/a><\/figure><\/div>\n\n\n\n

Monitored projects<\/strong><\/h4>\n\n\n\n

A Google Cloud project or AWS account can be monitored by exactly 1 Workspace. A Workspace always monitors its Google Cloud host project. However, you can configure a Workspace to monitor up to 100 Google Cloud projects and AWS accounts.<\/p>\n\n\n\n

Further, if you plan to use a Workspace to monitor more than the host project. Then, the best practice is to use a new, empty Google Cloud project to host the Workspace and then to add the projects and AWS accounts you want to monitor to your Workspace. However, this strategy lets you choose a useful name for your host project and Workspace. And, it gives you a little more flexibility in moving monitored projects between Workspaces. <\/p>\n\n\n\n

Billing<\/strong><\/h4>\n\n\n\n

There is no charge for creating a Workspace.<\/p>\n\n\n\n

Charges for logging and metric data ingested by the monitored projects are associated with that projects’ billing account. For AWS accounts, this means the billing accounts of the AWS connector projects:<\/p>\n\n\n\n