Pulling refs/heads/main into main

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

@@ -53,7 +53,7 @@ To authenticate using your service account keys go to the GCP console and follow
 
 #. Activate Key type :guilabel:`JSON`, and select :guilabel:`CREATE`. A new service account key JSON file is then downloaded to your computer. You will need this key to authenticate in the :guilabel:`Import Service Account Key` step in Splunk Observability Cloud.
 
-#. In a new window or tab, go to :new-page:`Cloud Resource Manager API <https://console.cloud.google.com/apis/library/cloudresourcemanager.googleapis.com?pli=1>`, and activate the Cloud Resource Manager API. You need to activate this API so Splunk Observability Cloud can use it to validate permissions on the service account keys.
+#. In a new window or tab, go to :new-page:`Cloud Monitoring API <https://cloud.google.com/monitoring/api/v3>` and activate it. Splunk Observability Cloud uses this API to validate permissions on the service account keys.
 
 For more information, refer to GCP's docs on :new-page:`Service account keys <https://cloud.google.com/iam/docs/service-account-creds#key-types>`. 
 

gdi/opentelemetry/components/sqlquery-receiver.rst

@@ -50,6 +50,20 @@ Next, include the receiver in the ``metrics`` pipeline of the ``service`` sectio
 
 See :ref:`sql-query-receiver-queries-example` for a complete config example.
 
+Sample configuration for a MySQL datasource using TCP
+----------------------------------------------------------------
+
+This is an example to connect a MySQL datasource to a database through a socket with autocommit mode enabled with ``user@unix(/mysql/run/mysql.sock)/schema/autocommit=true``:
+
+.. code-block:: yaml
+
+    receivers:
+      sqlquery:
+        driver: mysql
+        datasource: "user:password@tcp(host:port)/schema"
+        queries:
+          - sql: "your_query"
+
 Advanced configuration
 ----------------------------------