Adding a Google Cloud Platform (GCP) integration requires establishing a trust relationship between GCP and VMware Aria Operations for Applications (formerly known as Tanzu Observability by Wavefront). Minimum required permissions you need depend on the services that you are using. See Google Cloud Platform Overview and Permissions for details.
The overall process involves the following:
- Creating a service account in Google Cloud
- Giving that account viewer privileges
- Downloading a JSON private key
To register a Google Cloud Platform integration:
-
In the Name text box, enter a meaningful name.
-
In the JSON key text box, enter your JSON key to give read-only access to a GCP project. Note: The JSON key is securely stored and never exposed except for read-only access to the GCP APIs.
-
(Optional) Select the categories to fetch.
-
(Optional) In the Metric Allow List text box, you can add metrics to an allow list by entering a regular expression.
For example, to monitor all the CPU metrics coming from the Compute Engine, enter
^gcp.compute.instance.cpu.*$
.Note: Metric names consist of the actual metric name and a suffix (starting with an underscore ("_") or a dot (".")). The suffix represents an aggregation type. In the regular expression, you must use the actual metric names without the aggregation types, such as:
count
,rate
,min
,max
,sumOfSquaredDeviation
,mean
, and so on.For example, for the Google Cloud Pub/Sub Engine, we collect a number of metrics, and some of them contain a suffix:
Push request latencies metrics:
gcp.pubsub.subscription.push_request_latencies.bucket
gcp.pubsub.subscription.push_request_latencies.count
gcp.pubsub.subscription.push_request_latencies.mean
gcp.pubsub.subscription.push_request_latencies.sumOfSquaredDeviation
Here, the actual metric name is
gcp.pubsub.subscription.push_request_latencies
, whilebucket
,count
,mean
, andsumOfSquaredDeviation
are the aggregation types. When you create the regular expression, you must use onlygcp.pubsub.subscription.push_request_latencies
. For example,^gcp.pubsub.subscription.push_request_latencies$
.Cumulative count of messages acknowledged by Acknowledge requests, grouped by delivery type:
gcp.pubsub.subscription.ack_message_count_count
gcp.pubsub.subscription.ack_message_count_rate
Here, the actual metric name is
gcp.pubsub.subscription.ack_message_count
, while_count
and_rate
are the aggregation types. When you create the regular expression, you must use onlygcp.pubsub.subscription.ack_message_count
. For example,^gcp.pubsub.subscription.ack_message_count$
. -
(Optional) In the Additional Metric Prefixes text box, enter a comma separated list of additional metrics prefixes. The metrics names that start with these prefixes will be imported in addition to what you have selected as categories.
-
(Optional) Change the Service Refresh Rate. The default is
5
minutes. -
(Optional) Select whether you want to enable Histogram metrics ingestion.
-
(Optional) Select which histogram metrics to ingest.
- All - The default option which means that all metrics will be ingested.
- Custom - Allows you to ingest particular histogram metrics based on their Google Cloud Platform grouping functions, such as Count, Mean, and Standard Deviation. When you select a grouping function, only the histogram metrics with the respective grouping function will be ingested. If you deselect all check boxes, all histogram metrics will be ingested.
-
(Optional) Select to enable Detailed Histogram Metrics, Delta Counts, and Pricing & Billing information.
Note: Enabling Detailed Histogram Metrics and Delta Counts will increase your ingestion rate and costs.
If you select to enable the Pricing & Billing information, you must also provide an API key.
-
-
Click Register.