Provisioning Stackdriver workspaces
In this tutorial we will learn and understand about Provisioning Stackdriver workspaces.
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.
Host projects
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.
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.
Monitored projects
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.
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.
Billing
There is no charge for creating a Workspace.
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:
- Firstly, for Google Cloud projects. If you have VM instances that contain software that sends monitoring data or logs to Cloud Monitoring APIs, then you are charged for that data. This software includes the Monitoring agents, Logging agents, and third party libraries like Prometheus that you might install. You continue to accrue charges while that software is running.
- Secondly, when you add an AWS account to a Workspace, monitoring and logging data is sent by Cloud Monitoring agents, Cloud Logging agents, or other software to the AWS connector project, whose billing account receives any charges.
To stop all Cloud Monitoring charges for metrics usage, do one of the following:
- Firstly, disable the Monitoring APIs
- Secondly, stop Cloud Monitoring agents, Cloud Logging agents, and other software modules from sending metrics or logs to your Google Cloud project, or to the AWS connector projects.
Disabling Monitoring
To disable the collection of Monitoring data in your Google Cloud project, do the following:
- Firstly, from the Cloud Console, select the Google Cloud project or the AWS connector project, and then go to APIs & Services:
- Then, select Cloud Monitoring API.
- Lastly, click Disable API
Reference: Google Documentation