You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, Splunk Observability Cloud monitors all supported services, and any new services added later are also monitored. When you set integration parameters, you can choose to import metrics from a subset of the available services.
58
+
By default, Splunk Observability Cloud monitors all supported services, and any new services added later are also monitored. When you set the parameters for your integration you can choose to import metrics from a subset of the available services.
59
59
60
-
1. Log in to Splunk Observability Cloud and open the :new-page:`Google Cloud Platform guided setup <https://login.signalfx.com/#/integrations/gcp>`. Optionally, you can navigate to the guided setup on your own:
60
+
.. note:: Splunk is not responsible for data availability, and it can take up to several minutes (or longer, depending on your configuration) from the time you connect until you start seeing valid data from your account.
61
+
62
+
Log in to Splunk Observability Cloud and open the :new-page:`Google Cloud Platform guided setup <https://login.signalfx.com/#/integrations/gcp>`. Optionally, you can navigate to the guided setup on your own:
63
+
64
+
#. In the left navigation menu, select :menuselection:`Data Management`.
65
+
66
+
#. Go to the :guilabel:`Available integrations` tab, or select :guilabel:`Add Integration` in the :guilabel:`Deployed integrations` tab.
67
+
68
+
#. In the integration filter menu, select :guilabel:`By Use Case`, and select the :guilabel:`Monitor Infrastructure` use case.
69
+
70
+
#. In the :guilabel:`Cloud Integrations` section, select the :guilabel:`Google Cloud Platform` tile to open the Google Cloud Platform guided setup.
71
+
72
+
Authenticate with WIF
73
+
++++++++++++++++++++++++++++++++++++++++++++++++
74
+
75
+
1. In the wizard, select Workload Identity Federation (WIF) as the authentication method.
76
+
77
+
2. Continue to define the connection with GCP:
78
+
79
+
* Poll rate. Select the rate (in seconds) at which you want Splunk Observability Cloud to poll GCP for metric data, with 1 minute as the minimum unit, and 10 minutes as the maximum unit. For example, a value of 300 polls metrics once every 5 minutes.
80
+
81
+
* Specify if you want to use quota from the project where metrics are stored. See more at :ref:`gcp-quota`.
82
+
83
+
* Note that GCP metadata is automatically imported.
84
+
85
+
3. Prepare your GCP account following the steps on the UI.
86
+
87
+
4. Establish the connection:
61
88
62
-
#. In the left navigation menu, select :menuselection:`Data Management`.
89
+
* Name your integration.
63
90
64
-
#. Go to the :guilabel:`Available integrations` tab, or select :guilabel:`Add Integration` in the :guilabel:`Deployed integrations` tab.
91
+
* Import your WIF configuration.
92
+
93
+
* Add your projects.
65
94
66
-
#. In the integration filter menu, select :guilabel:`By Use Case`, and select the :guilabel:`Monitor Infrastructure` use case.
95
+
* Select your access token.
67
96
68
-
#. In the :guilabel:`Cloud Integrations` section, select the :guilabel:`Google Cloud Platform` tile to open the Google Cloud Platform guided setup.
97
+
5. Select the data to import.
69
98
70
-
2. Complete the following fields:
99
+
* Specify which GCP services you want to monitor.
100
+
101
+
* Optionally you can import additional data. See more at :ref:`gcp-additional-data`.
71
102
72
-
* Name. Type in the name of the GCP integration.
103
+
Your GCP integration is now complete!
73
104
74
-
* Project. Select :guilabel:`Add Project` to add a new project and follow the prompts to authenticate it. For more details, see :ref:`gcp-prereqs-authenticate`.
105
+
Authenticate with Service Account keys
106
+
++++++++++++++++++++++++++++++++++++++++++++++++
75
107
76
-
* Services. By default the new integration syncs with all supported GCP services. Select :guilabel:`All services > Sync only selected services` to select specific services to sync with.
108
+
1. In the wizard, select Service Account keys as the authentication method.
77
109
110
+
2. Continue to define the connection with GCP:
111
+
78
112
* Poll rate. Select the rate (in seconds) at which you want Splunk Observability Cloud to poll GCP for metric data, with 1 minute as the minimum unit, and 10 minutes as the maximum unit. For example, a value of 300 polls metrics once every 5 minutes.
79
113
80
-
* Specify data to import: Metadata and/or metrics.
114
+
* Specify if you want to use quota from the project where metrics are stored. See more at :ref:`gcp-quota`.
81
115
82
-
* Specify if you want to use quota from the project where metrics are stored. See :ref:`gcp-quota` for more information.
116
+
* Note that GCP metadata is automatically imported.
83
117
84
-
3. Optional fields:
118
+
3. Prepare your GCP account following the steps on the UI.
85
119
86
-
* Custom Metric Type Domains. 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``.
120
+
4. Establish the connection:
87
121
88
-
- 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>`.
122
+
* Name your integration.
89
123
90
-
- 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.
124
+
* Project. Add your projects' IDs and select :guilabel:`Import service account keys` to add a new project. Follow the prompts to authenticate it. For more details, see :ref:`gcp-prereqs-authenticate`.
91
125
92
-
* Compute Metadata Included List. 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>``.
126
+
* Select your access token.
93
127
94
-
Your GCP integration is now complete.
128
+
5. Select the data to import.
95
129
96
-
.. note:: Splunk is not responsible for data availability, and it can take up to several minutes (or longer, depending on your configuration) from the time you connect until you start seeing valid data from your account.
130
+
* Specify which GCP services you want to monitor.
131
+
132
+
* Optionally you can import additional data. See more at :ref:`gcp-additional-data`.
133
+
134
+
Your GCP integration is now complete!
97
135
98
136
.. _gcp-quota:
99
137
@@ -106,6 +144,21 @@ If you're using a single principal for multiple projects, GCP tracks all API usa
106
144
107
145
For a more detailed description see :new-page:`Principals <https://cloud.google.com/iam/docs/overview#concepts_related_identity>` in GCP's docs.
108
146
147
+
.. _gcp-additional-data:
148
+
149
+
Import additional data
150
+
++++++++++++++++++++++++++++++++++++++++++++++++
151
+
152
+
On step 5 of the guided set-up you can configure the import of the following additional data:
153
+
154
+
* Custom metric type domains. 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``.
155
+
156
+
- 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>`.
157
+
158
+
- 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.
159
+
160
+
* Compute metadata included list. 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