Managing workspaces

Cloud Monitoring uses Workspaces to organize and manage its information. 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. For a conceptual overview, see Workspaces.

Creating a Workspace

A Workspace can manage the monitoring data for a single Google Cloud project, or it can manage the data for multiple Google Cloud projects and AWS accounts. However, a Google Cloud project or an AWS account can only be associated with one Workspace at a time.

To create a Workspace to manage the monitoring data for an existing Google Cloud project, see Creating a Workspace.

To create a Workspace to manage the monitoring data for multiple Google Cloud projects or AWS accounts, see Creating your first multi-project Workspace and Multi-project Workspace best practices.

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 "Quickstart" is selected:

Monitoring navigation menu with Quickstart selected.

Granting Workspace access

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.

Authorization

To modify the members of the Google Cloud project, you must have the role of Project owner.

Procedure

To add users to your Workspace, do the following:

  1. In the Google Cloud Console, go to the IAM & admin page:

    Go to the IAM page

  2. From the list of projects, select your Workspace's host project. The Workspace and the host project have the same name.

  3. At the top of the page, click Add.

  4. In the New members box, enter a user, group, service account, or domain.

  5. 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

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 project. The impact is that deletion of the AWS connector project also deletes the logs.

Authorization

To remove a project from a Workspace, you must have the role of Project owner for the project that is to be removed.

Procedure

To remove a Google Cloud project or an AWS account from a Workspace, do the following:

  1. In the Cloud Console, select Monitoring:

    Go to Monitoring

  2. Select Settings.

  3. Ensure that the proper Workspace is selected.

  4. Click More for the Google Cloud project or an AWS account that you want to remove, click Remove from workspace.

  5. 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.

Authorization

To move a Google Cloud project from one Workspace to another Workspace, you must have one of the following roles on the Google Cloud project being moved and on the host project of the destination Workspace:

  • Project owner
  • Monitoring editor
  • Monitoring admin

To connect an AWS project to a different Workspace, you must have the role of Project owner for the AWS connector project, and you must have one of the roles in the preceding list for the host project of the destination Workspace.

Moving a (non-hosting) Google Cloud project

To move a non-host Google Cloud project to another Workspace, do the following:

  1. In the Google Cloud Console, select the Google Cloud project that you want to move to a different Workspace:

    Go to Cloud Console

  2. In the navigation pane, select Monitoring and then select Settings.

  3. Click More for the Google Cloud project that you want to move, click Move to another workspace.

  4. 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:

  1. Remove the AWS connector project from its Workspace by following the steps in Removing a project.
  2. Delete the AWS connector project.
  3. Add your AWS account to the desired Workspace by following the steps in Adding a monitored project.

Merging Workspaces

When you are administering Workspace A, you can merge into it a different workspace, say Workspace B. These are the effects of the merge operation:

  • All Google Cloud projects, except AWS connector projects projects, that were managed by Workspace B are moved into Workspace A. Metrics for the projects are also moved into Workspace A.

  • In Workspace A, 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 B is added to Workspace A.

    Merging is the only way to separate a host project from its Workspace.

  • After the merge completes, Workspace B isn't accessible.

Authorization

To merge two Workspaces, you must have one of the following roles on the host projects of both Workspaces:

  • Project owner
  • Monitoring editor
  • Monitoring admin

Process

To merge another workspace into Workspace A, do the following:

  1. In the Google Cloud Console, select the Google Cloud host project for Workspace A:

    Go to Cloud Console

  2. In the navigation pane, select Monitoring and then select Settings.

  3. Ensure that Workspace A is selected. You are now administering Workspace A. This is the Workspace that you want to keep.

  4. Click Merge.

  5. Select the Workspace that you want to merge into Workspace A. For example, if you want to merge Workspace B into Workspace A, then select Workspace B.

  6. 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.

Authorization

To delete a Workspace, you must have the role of Project owner for the Workspace's host project.

Process

If your Workspace project has no resources you want to preserve, then delete the Workspace by deleting the Workspace's host project:

  1. In the Cloud Console, go to the IAM & admin console:

    Go to the IAM console

  2. Ensure that the host project is selected in the menu bar of the Cloud Console.

  3. Click Settings.

  4. Click Shut Down .

Viewing your workspaces

To view all of your Workspaces, click Menu in the navigation panel:

Display of the most recently visited workspaces.

  • 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 and Backward buttons.
    • To filter the list, enter a partial name or project identifier.

Troubleshooting

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:

  • google.com
  • accounts.google.com
  • apis.google.com

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:

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.