Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit 20ec35e

Browse files
Feedback
1 parent 5c6e126 commit 20ec35e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

gdi/get-data-in/connect/gcp/gcp-connect.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -103,10 +103,10 @@ Options
103103

104104
Optionally you can:
105105

106-
* To list any additional GCP service domain names that you want to monitor, use commas to separate domain names in the :strong:`Custom Metric Type Domains` field.
107-
108-
- For example, to obtain Apigee metrics, add ``apigee.googleapis.com``.
109-
106+
* To list any additional GCP service domain names that you want to monitor, use commas to separate domain names in the :strong:`Custom Metric Type Domains` field. For example, to obtain Apigee metrics, add ``apigee.googleapis.com``.
107+
108+
- For information on the available GCP metric domains refer to the official GCP docs at :new-page:`Google Cloud metrics <https://cloud.google.com/monitoring/api/metrics_gcp>`.
109+
110110
- To learn about custom metric type domain syntax, see :new-page:`Custom metric type domain examples <https://dev.splunk.com/observability/docs/integrations/gcp_integration_overview#Custom-metric-type-domain-examples>` in the Splunk developer documentation.
111111

112112
* If you select Compute Engine as one of the services to monitor, you can enter a comma-separated list of Compute Engine Instance metadata keys to send as properties. These metadata keys are sent as properties named ``gcp_metadata_<metadata-key>``.

0 commit comments

Comments
 (0)