Setting Up Application Performance Monitoring on Google Cloud Projects: CPU, Memory, and Disk Monitoring

How to Set Up Application Performance Monitoring on Google Cloud Projects

Question

You are asked to set up application performance monitoring on Google Cloud projects A, B, and C as a single pane of glass.

You want to monitor CPU, memory, and disk.

What should you do?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

C.

To set up application performance monitoring on Google Cloud projects A, B, and C as a single pane of glass, the following steps should be taken:

  1. Enable Monitoring API: The first step is to enable the Monitoring API in Google Cloud Console for all three projects A, B, and C. This API allows access to various metrics for the resources used by applications running on Google Cloud.

  2. Create a Workspace: Next, create a new Workspace in Google Cloud Console. A Workspace is a container for a set of dashboards, alerts, and other Monitoring resources. To create a Workspace, select the Monitoring menu and then click on Workspaces, and then click on Create Workspace.

  3. Add Projects: Once a Workspace is created, you can add projects to it by selecting the Workspace and then clicking on the Add More Projects button. You can then add projects A, B, and C to the Workspace.

  4. Configure Metrics: After adding projects to the Workspace, you can configure the metrics to monitor CPU, memory, and disk usage. To do this, go to the Metrics Explorer in Google Cloud Console and select the appropriate metric. You can then configure charts to display the metric data.

  5. Share Dashboards: Finally, you can share the dashboards created in the Workspace with other users who need access to the monitoring data. To do this, select the dashboard and click on the Share button.

Option A is incorrect because it suggests sharing charts from each project separately, which would not provide a single pane of glass view.

Option B is partially correct because it suggests giving the metrics.reader role to projects A, B, and C, which would allow access to the monitoring data. However, it does not mention creating a Workspace or configuring the metrics, which are necessary for a single pane of glass view.

Option C is incorrect because it suggests using default dashboards to view all projects in sequence, which would not provide a single pane of glass view.

Option D is partially correct because it suggests creating a Workspace under project A and adding projects B and C to it. However, it does not mention configuring the metrics or sharing the dashboards, which are necessary for a single pane of glass view.