This page explains how to manage Workspaces. Your Google Cloud projects and Amazon Web Service (AWS) accounts must be members of a Workspace before they can be monitored.
Creating a Workspace
For information on creating a Workspace, creating a multi-project Workspace, and for adding projects to a Workspace, see Creating a Workspace.
Selecting a Workspace
After you create a Workspace, the navigation panel lists your current Workspace and includes a menu that you can use to select a different Workspace.
In the following screenshot, the Workspace "A Sample Project" is selected:
Adding users to a Workspace
To give users access to a Workspace, you need to add them to the Workspace host project with a role that grants the desired access level. To modify the members of the Google Cloud project, you must have the role of Owner.
To add users to your Workspace, do the following:
In the Google Cloud Console, go to the IAM & admin page:
From the list of projects, select your Workspace's host project. The Workspace and the host project have the same name.
At the top of the page, click Add.
In the New members box, enter a user, group, service account, or domain.
Assign a Project role to the new member. In the role selector, enter Monitoring to view roles limited to monitoring-level access. The role Project owner grants full project-level access, including access to monitoring. After you make your selection, click Save.
Removing a project or account from a Workspace
To remove a project from a Workspace, you must be an owner of the project. Removing a project, moving a project, and merging Workspaces all might result in loss of some configuration information. For example, if you move a project, group definitions aren't moved. Before taking any of theses actions, make sure you take the right action for your situation:
If you want to stop accruing charges, see Billing.
If you want to remove a host project from its Workspace or move a host project to a different Workspace, you must perform a merge. After the merge operation, your Google Cloud project is no longer a host project and therefore it can be removed from its Workspace or moved to a different Workspace.
If you want to change the Workspace associated with a Google Cloud project, move the project. For more information, see Moving a project.
If you want to move an AWS account from one Workspace to another Workspace, you must remove the AWS connector project and delete that project. You cannot use the AWS connector project with another Workspace. You can then add your AWS account to another Workspace, letting Monitoring create a new connector project. For more information, see Adding a monitored project.
If you use Cloud Logging, the logs are stored with the AWS connector account. The impact is that deletion of the AWS connector project also deletes the logs.
To remove a Google Cloud project or an AWS account from a Workspace, do the following:
In the Cloud Console, select Monitoring:
Ensure that the proper Workspace is selected.
Click More more_vert for the Google Cloud project or an AWS account that you want to remove, click Remove from workspace.
If you removed an AWS account from a Workspace, you removed the AWS connector project, which represents the AWS account. You cannot use the AWS connector project with another Workspace. Delete the connector project.
Moving a project to a different Workspace
When you move a Google Cloud project to a different Workspace, you move the project and its metrics:
- Alerting policies and uptime checks aren't moved.
- Group definitions aren't moved but group membership might decrease in the Workspace losing the project and increase in the Workspace gaining the project.
- Dashboards and charts aren't moved. However, the content of the dashboards and charts might change in both Workspaces due to the movement of metrics.
Moving a (non-hosting) Google Cloud project
You must have one of the following roles on both the project and the destination Workspace to move a project from one Workspace to another Workspace:
- Project owner
- Monitoring editor
- Monitoring admin
To move a non-host Google Cloud project to another Workspace, do the following:
In the Google Cloud Console, select the Google Cloud project that you want to move to a different Workspace:
In the navigation pane, select Monitoring and then select Settings.
Click More more_vert for the Google Cloud project that you want to move, click Move to another workspace.
Select the new Workspace and click Move.
Moving a hosting project
To move the host project from a Workspace to another Workspace, follow the instructions in Merging Workspaces.
Moving an AWS account
To move an AWS account from one Workspace to another Workspace, do the following:
- Remove the AWS connector project from its Workspace by following the steps in Removing a project.
- Delete the AWS connector project.
- Add your AWS account to the desired Workspace by following the steps in Adding a monitored project.
Merging Workspace A into Workspace B moves all the Google Cloud projects except AWS connector projects from Workspace A to Workspace B. Specifically, here is the effect of merging A into B:
All Google Cloud projects that were added to Workspace A are moved into Workspace B. Metrics for the projects are also moved into Workspace B. However, dashboards, resource groups, uptime checks, notification channels, and alerting policies aren't moved into Workspace B.
In Workspace B, existing dashboards and charts might have more data, and groups might have more members. These changes are due to the inclusion of additional metrics and are dependent on your configuration choices. In addition, uptime checks and alerting policies might be impacted.
The host project for Workspace A is added to Workspace B.
Merging is the only way to separate a host project from its Workspace.
After the merge completes, Workspace A isn't accessible.
To merge Workspace A into Workspace B, do the following:
In the Google Cloud Console, select the Google Cloud host project for Workspace B:
In the navigation pane, select Monitoring and then select Settings.
Ensure that Workspace B is selected. This is the Workspace that you want to keep.
Select Workspace A. You want to merge Workspace A into Workspace B.
Review the information that is lost during the merge. If you agree to that information loss, click Merge.
Deleting a Workspace
Before deleting a Workspace, check if the project you used to create the Workspace has resources you want to preserve, or if the Workspace is still linked to additional Google Cloud projects or AWS accounts. If so, see Merging Workspaces for a way to move resources to another place before deleting the Workspace.
If your Workspace project has no resources you want to preserve, then delete the Workspace by deleting the Workspace's host project:
In the Cloud Console, go to the IAM & admin console:
Ensure that the host project is selected in the menu bar of the Cloud Console.
Click Shut Down delete.
Viewing your workspaces
To view all of your Workspaces, click Menu arrow_drop_down in the navigation panel:
- The Recent tab displays your more recently access Workspaces. You can filter and sort the display.
- The All tab displays all accessible Workspaces:
- To page through the Workspaces, use the Forward arrow_forward_ios and Backward arrow_back_ios buttons.
- To filter the list, enter a partial name or project identifier.
I can't log in to my Workspace
Cloud Monitoring relies on cookies from various Google sites to manage Workspaces. If these cookies are blocked, you may find that you:
Cannot get past the Log in with Google dialog, and you see a message saying “Cookies aren't enabled in current environment”.
Get stuck in an endless authentication loop.
Cookies can be blocked accidentally, or by automatic updates pushed out as part of changes in security policy at your location.
You must have third-party cookies enabled for the following:
For information on enabling cookies, see your browser's documentation:
My email address isn't accepted
Monitoring doesn't accept email addresses containing an apostrophe, although Google Cloud does. Users with such email addresses are unrecognized when they attempt to use Monitoring.
I can't add a project to a Workspace because it's already in another Workspace
Projects can be associated with only one Workspace at a time:
- You can move monitored projects to another Workspace.
- You can move a Workspace's host project by merging Workspaces.
- You cannot move AWS accounts. You must remove the AWS account from its current Workspace and add it to a new Workspace, going through the AWS authorization process again. For more information, go to Removing a project from a Workspace.
Project resources are missing from Monitoring
It can take ten minutes or so before Monitoring notices new or removed resources, such as VM instances, in your projects.
If you start a service such as Compute Engine in a project that is associated with a Workspace, it can take a hour or more for Monitoring to notice the new service. Until that time, the service's resource types don't appear in any Monitoring menus.
How do I use Workspaces with Logging?
Cloud Logging doesn't use Workspaces. By using advanced log filters, you can view or manage log entries from multiple Google Cloud projects or AWS accounts.
In the case of AWS accounts, you access logs through the AWS connector project that Monitoring creates when you add the account to a Workspace. Therefore, you do have to add your account to a Workspace and install the Cloud Logging agent on your VM instances in order to receive your logs.