gcp doc only app - Batch 1

cid-redirects.json

@@ -2482,6 +2482,26 @@
   "/cid/14323": "/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/docusign-source",
   "/cid/14326": "/docs/integrations/global-intelligence/kubernetes-devops",
   "/cid/30001": "/docs/integrations/microsoft-azure/azure-batch",
+  "/cid/21001": "/docs/integrations/google/cloud-alloydb-for-postgresql",
+  "/cid/21002": "/docs/integrations/google/cloud-api-gateway",
+  "/cid/21003": "/docs/integrations/google/cloud-apis",
+  "/cid/21004": "/docs/integrations/google/cloud-armor",
+  "/cid/21005": "/docs/integrations/google/cloud-auto-scaler",
+  "/cid/21006": "/docs/integrations/google/cloud-backup-for-gke",
+  "/cid/21007": "/docs/integrations/google/cloud-bigquery-bi-engine",
+  "/cid/21008": "/docs/integrations/google/cloud-bigtable",
+  "/cid/21009": "/docs/integrations/google/cloud-certificate-authority-service",
+  "/cid/21010": "/docs/integrations/google/cloud-certificate-manager",
+  "/cid/21011": "/docs/integrations/google/cloud-composer",
+  "/cid/21012": "/docs/integrations/google/cloud-dataflow",
+  "/cid/21013": "/docs/integrations/google/cloud-dataproc-metastore",
+  "/cid/21014": "/docs/integrations/google/cloud-dataproc",
+  "/cid/21015": "/docs/integrations/google/cloud-datastore",
+  "/cid/21016": "/docs/integrations/google/cloud-datastream",
+  "/cid/21018": "/docs/integrations/google/cloud-deploy",
+  "/cid/21019": "/docs/integrations/google/cloud-filestore",
+  "/cid/21020": "/docs/integrations/google/cloud-firebase",
+  "/cid/21021": "/docs/integrations/google/cloud-firestore",
   "/Cloud_SIEM_Enterprise": "/docs/cse",
   "/Cloud_SIEM_Enterprise/Administration": "/docs/cse/administration",
   "/Cloud_SIEM_Enterprise/Administration/Cloud_SIEM_Enterprise_Feature_Update_(2022)": "/docs/cse/administration",

docs/integrations/google/cloud-alloydb-for-postgresql.md

@@ -0,0 +1,34 @@
+
+---
+id: cloud-alloydb-for-postgresql
+title: Google Cloud AlloyDB for PostgreSQL
+sidebar_label: Google Cloud AlloyDB for PostgreSQL
+description: Learn about the Sumo Logic collection process for the Google Cloud AlloyDB for PostgreSQL service.
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<img src={useBaseUrl('img/integrations/google/GoogleCloudAlloyDBforPostgreSQL.png')} alt="Thumbnail icon" width="50"/>
+
+
+AlloyDB for PostgreSQL is a fully managed, PostgreSQL-compatible database service that's designed for your most demanding workloads, including hybrid transactional and analytical processing. For more details, refer to the GCP [documentation](https://cloud.google.com/alloydb/docs/overview)
+
+## Log types
+
+* [Platform Logs](https://docs.aws.amazon.com/appflow/latest/userguide/monitoring-cloudwatch.html)
+* [Audit Logs](https://docs.aws.amazon.com/appflow/latest/userguide/appflow-cloudtrail-logs.html)
+
+## Setup
+You can collect the logs for Sumo Logic's Google Cloud AlloyDB for PostgreSQL integration by following the below steps.
+
+### Configure logs collection
+
+* Collect **Audit Logs** using [Google Cloud Platform source](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source). Refer to the [permissions and roles](https://cloud.google.com/alloydb/docs/audit-logging#audit_log_permissions) required for accessing audit logs. To enable logging for Google AlloyDB refer to [Google documentation](https://cloud.google.com/alloydb/docs/audit-logging#enabling_audit_logging). For more detail, on AlloyDB operations being audited refer to [audited operations](https://cloud.google.com/alloydb/docs/audit-logging#audited_operations). While creating the sync in GCP, as part of the **Choose logs to include in sink** section you can use the following query:
+   ```sql
+   (resource.type=audited_resource resource.labels.service=alloydb.googleapis.com)
+   ```
+
+* Collect **Platform Logs** using [Google Cloud Platform source](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source). AlloyDB platform logs include logs related to [pgAudit](https://cloud.google.com/alloydb/docs/pgaudit/about) and instance log which includes - PostgreSQL database logs, container logs for dataplane agents, internal dogfish logs. To enabled pgAudit logs follow the instruction [here](https://cloud.google.com/alloydb/docs/pgaudit/enable-audit). While creating the sync in GCP, as part of the **Choose logs to include in sink** section, you can use the following query:
+   ```sql
+   (resource.type=alloydb.googleapis.com/Instance)
+   ```

docs/integrations/google/cloud-api-gateway.md

@@ -0,0 +1,33 @@
+
+---
+id: cloud-api-gateway
+title: Google Cloud API Gateway
+sidebar_label: Google Cloud API Gateway
+description: Learn about the Sumo Logic collection process for the Google Cloud API Gateway service.
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<img src={useBaseUrl('img/integrations/google/GoogleCloudAPIGateway.png')} alt="Thumbnail icon" width="50"/>
+
+With API Gateway, you can create, secure, and monitor APIs for Google Cloud serverless back ends, including Cloud Functions, Cloud Run, and App Engine. For more details, refer to the [GCP documentation](https://cloud.google.com/api-gateway/docs/how-to).
+
+## Log types
+
+* [Platform Logs](https://docs.aws.amazon.com/appflow/latest/userguide/monitoring-cloudwatch.html)
+* [Audit Logs](https://docs.aws.amazon.com/appflow/latest/userguide/appflow-cloudtrail-logs.html)
+
+## Setup
+You can collect the logs and metrics for Sumo Logic's Google Cloud API Gateway integration by following the below steps.
+
+### Configure logs collection
+
+* Collect **Audit Logs** using [Google Cloud Platform source](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source). Refer to the [permissions and roles](https://cloud.google.com/api-gateway/docs/audit-logging#audit_log_permissions) required for accessing audit logs. To enable logging for Google API Gateway refer to [Google documentation](https://cloud.google.com/api-gateway/docs/audit-logging#enabling_audit_logging). For more detail, on API Gateway operations being audited refer to [audited operations](https://cloud.google.com/api-gateway/docs/audit-logging#audited_operations). While creating the sync in GCP, as part of the **Choose logs to include in sink** section you can use the following query:
+   ```sql
+   (resource.type=apigateway.googleapis.com/Gateway OR (resource.type=audited_resource AND resource.labels.service=apigateway.googleapis.com))
+   ```
+
+* Collect **Platform Logs** using [Google Cloud Platform source](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source). While creating the sync in GCP, as part of the **Choose logs to include in sink** section, you can use the following query:
+   ```sql
+   (resource.type=apigateway.googleapis.com/Gateway)
+   ```

docs/integrations/google/cloud-apis.md

@@ -0,0 +1,27 @@
+
+---
+id: cloud-apis
+title: Google Cloud APIs
+sidebar_label: Google Cloud APIs
+description: Learn about the Sumo Logic collection process for the Google Cloud APIs service.
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<img src={useBaseUrl('img/integrations/google/GoogleCloudAPIs.png')} alt="Thumbnail icon" width="50"/>
+
+Google Cloud APIs are programmatic interfaces to Google Cloud Platform services. For more details, refer to the [GCP documentation](https://cloud.google.com/apis/docs/monitoring).
+
+## Metric types
+
+* [Google Cloud Metrics](https://cloud.google.com/monitoring/api/metrics_gcp)
+
+
+## Setup
+You can collect the metrics for Sumo Logic's Google Cloud API's integration by following the below steps.
+
+### Configure metrics collection
+
+* Collect **GCP Metrics** using the [GCP Metric](/docs/send-data/hosted-collectors/google-source/gcp-metrics-source/) source. Note that in the Services dropdown, you'll need to select **Cloud APIs**. For Google Cloud API metrics and dimensions, refer to [Google API metrics](https://cloud.google.com/monitoring/api/metrics_gcp#gcp-serviceruntim).
+
+

docs/integrations/google/cloud-armor.md

@@ -0,0 +1,30 @@
+
+---
+id: cloud-armor
+title: Google Cloud Armor
+sidebar_label: Google Cloud Armor
+description: Learn about the Sumo Logic collection process for the Google Cloud Armor service.
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<img src={useBaseUrl('img/integrations/google/GoogleCloudArmor.png')} alt="Thumbnail icon" width="50"/>
+
+Google Cloud Armor helps you protect your Google Cloud deployments from multiple types of threats, including distributed denial-of-service (DDoS) attacks and application attacks like cross-site scripting (XSS) and SQL injection (SQLi). For more details, refer to the [GCP documentation](https://cloud.google.com/armor/docs/cloud-armor-overview)
+
+## Log types
+
+* [Platform Logs](https://docs.aws.amazon.com/appflow/latest/userguide/monitoring-cloudwatch.html)
+* [Audit Logs](https://docs.aws.amazon.com/appflow/latest/userguide/appflow-cloudtrail-logs.html)
+
+## Setup
+You can collect the logs for Sumo Logic's Google Cloud Armor integration by following the below steps.
+
+### Configure logs collection
+
+* Collect **Audit Logs** using [Google Cloud Platform source](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source). Refer to the [permissions and roles](https://cloud.google.com/armor/docs/audit-logging#audit_log_permissions) required for accessing audit logs. To enable logging for Google Armor refer to [Google documentation](https://cloud.google.com/armor/docs/audit-logging#enabling_audit_logging). For more detail, on Cloud Armor operations being audited refer to [audited operations](https://cloud.google.com/armor/docs/audit-logging#audited_operations). While creating the sync in GCP, as part of the **Choose logs to include in sink** section you can use the following query:
+   ```sql
+   (resource.type=(backendServices or securityPolicies) resource.labels.service=compute.googleapis.com)
+   ```
+
+* Collect **Platform Logs** using [Google Cloud Platform source](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source). Google Cloud Armor logs are part of the Cloud Load Balancing logs. To enable these logs follow the instruction [here](https://cloud.google.com/armor/docs/request-logging). For collecteing request logs, copy the query from log explorer which you get after following [these](https://cloud.google.com/armor/docs/request-logging#view-logs) steps and while creating the sync in GCP, as part of the **Choose logs to include in sink** section, you can use the same query.

docs/integrations/google/cloud-auto-scaler.md

@@ -0,0 +1,32 @@
+
+---
+id: cloud-auto-scaler
+title: Google Cloud Auto Scaler
+sidebar_label: Google Cloud Auto Scaler
+description: Learn about the Sumo Logic collection process for the Google Cloud Auto Scaler service.
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<img src={useBaseUrl('img/integrations/google/GoogleAutoScaler.png')} alt="Thumbnail icon" width="50"/>
+
+Managed instance groups (MIGs) offer autoscaling capabilities that let you automatically add or delete virtual machine (VM) instances from a MIG based on increases or decreases in load. Autoscaling helps your apps gracefully handle increases in traffic and reduce costs when the need for resources is lower. For more details, refer to the [GCP documentation](https://cloud.google.com/compute/docs/autoscaler).
+
+## Log and Metric types
+
+* [Google Cloud Metrics](https://cloud.google.com/monitoring/api/metrics_gcp)
+* [Platform Logs](https://docs.aws.amazon.com/appflow/latest/userguide/monitoring-cloudwatch.html)
+
+## Setup
+You can collect the logs and metrics for Sumo Logic's Google Cloud Auto Scaler integration by following the below steps.
+
+### Configure logs collection
+
+* Collect **Platform Logs** using [Google Cloud Platform source](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source).When you enable autoscaling, the autoscaler makes scaling decisions based on the options that you specify. Each scaling decision is logged by Cloud Logging which can be collected, [here](https://cloud.google.com/compute/docs/autoscaler/viewing-autoscaler-logs) are the details. While creating the sync in GCP, as part of the **Choose logs to include in sink** section, you can use the following query:
+   ```sql
+   (resource.type=autoscaler)
+   ```
+
+### Configure metrics collection
+
+* Collect **GCP Metrics** using the [GCP Metric](/docs/send-data/hosted-collectors/google-source/gcp-metrics-source/) source. Note that in the Services dropdown, you'll need to select **Auto Scaler**. For Google Auto Scaler metrics and dimensions, refer to [Google Auto Scaler metrics](https://cloud.google.com/monitoring/api/metrics_gcp#gcp-autoscaler).

docs/integrations/google/cloud-backup-for-gke.md

@@ -0,0 +1,35 @@
+
+---
+id: cloud-backup-for-gke
+title: Google Cloud Backup for GKE
+sidebar_label: Google Cloud Backup for GKE
+description: Learn about the Sumo Logic collection process for the Google Cloud Backup for GKE service.
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<img src={useBaseUrl('img/integrations/google/GoogleCloudBackupforGKE.png')} alt="Thumbnail icon" width="50"/>
+
+
+Backup for GKE is a service for backing up and restoring workloads in GKE clusters. For more details, refer to the [GCP documentation](https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/concepts/backup-for-gke).
+
+## Log types
+
+* [Platform Logs](https://docs.aws.amazon.com/appflow/latest/userguide/monitoring-cloudwatch.html)
+* [Audit Logs](https://docs.aws.amazon.com/appflow/latest/userguide/appflow-cloudtrail-logs.html)
+
+## Setup
+
+You can collect the logs for Sumo Logic's Google Cloud Backup for GKE integration by following the below steps.
+
+### Configure logs collection
+
+* Collect **Audit Logs** using [Google Cloud Platform source](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source). Refer to the [permissions and roles](https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/how-to/audit-logging#audit_log_permissions) required for accessing audit logs. To enable logging for Google Backup for GKE refer to [Google documentation](https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/how-to/audit-logging). For more detail, on Backup for GKE operations being audited refer to [audited operations](https://cloud.google.com/kubernetes-engine/docs/audit-logging#audited_operations). While creating the sync in GCP, as part of the **Choose logs to include in sink** section you can use the following query:
+   ```sql
+   (resource.type=audited_resource AND resource.labels.service=gkebackup.googleapis.com)
+   ```
+
+* Collect **Platform Logs** using [Google Cloud Platform source](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source). Here are the details of [platforms logs for Backup for GKE](https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/how-to/platform-logging-backup-for-gke). While creating the sync in GCP, as part of the **Choose logs to include in sink** section, you can use the following query:
+   ```sql
+   (resource.type=(gkebackup.googleapis.com/BackupPlan or gkebackup.googleapis.com/RestorePlan))
+   ```

docs/integrations/google/cloud-bigquery-bi-engine.md

@@ -0,0 +1,28 @@
+
+---
+id: cloud-bigquery-bi-engine
+title: Google Cloud BigQuery BI Engine
+sidebar_label: Google Cloud BigQuery BI Engine
+description: Learn about the Sumo Logic collection process for the Google Cloud BigQuery BI Engine service.
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<img src={useBaseUrl('img/integrations/google/GoogleCloudBigQueryBIEngine.png')} alt="Thumbnail icon" width="50"/>
+
+BigQuery BI Engine is a fast, in-memory analysis service that accelerates many SQL queries in BigQuery by intelligently caching the data you use most frequently. For more details, refer to the [GCP documentation](https://cloud.google.com/bigquery/docs/bi-engine-intro).
+
+## Log types
+
+* [Platform Logs](https://docs.aws.amazon.com/appflow/latest/userguide/monitoring-cloudwatch.html)
+
+## Setup
+You can collect the logs for Sumo Logic's Google Cloud Bigquery BI engine integration by following the below steps.
+
+### Configure logs collection
+
+* Collect **Platform Logs** using [Google Cloud Platform source](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source). While creating the sync in GCP, as part of the **Choose logs to include in sink** section, you can use the following query:
+   ```sql
+   (resource.type="bigquery_biengine_model")
+   ```
+

docs/integrations/google/cloud-bigtable.md

@@ -0,0 +1,42 @@
+---
+id: cloud-bigtable
+title: Google Cloud Bigtable
+sidebar_label: Google Cloud Bigtable
+description: Learn about the Sumo Logic collection process for the Google Cloud Bigtable service.
+---
+
+import useBaseUrl from '@docusaurus/useBaseUrl';
+
+<img src={useBaseUrl('img/integrations/google/GoogleCloudBigtable.png')} alt="Thumbnail icon" width="50"/>
+
+Bigtable is a fully managed wide-column and key-value NoSQL database service for large analytical and operational workloads. For more details, refer to the [GCP documentation](https://cloud.google.com/bigtable/docs/overview).
+
+## Log and Metric types
+
+* [Google Cloud Metrics](https://cloud.google.com/monitoring/api/metrics_gcp)
+* [Platform Logs](https://docs.aws.amazon.com/appflow/latest/userguide/monitoring-cloudwatch.html)
+* [Audit Logs](https://docs.aws.amazon.com/appflow/latest/userguide/appflow-cloudtrail-logs.html)
+
+## Setup
+
+You can collect the logs and metrics for Sumo Logic's Google Cloud Bigtable integration by following the below steps.
+
+### Configure logs collection
+
+* Collect **Audit Logs** using [Google Cloud Platform source](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source). Refer to the [permissions and roles](https://cloud.google.com/bigtable/docs/audit-logging#audit_log_permissions) required for accessing audit logs. To enable logging for Google BigTable refer to [Google documentation](https://cloud.google.com/bigtable/docs/audit-logging#enabling_audit_logging). For more detail, on Bigtable operations being audited refer to [audited operations](https://cloud.google.com/bigtable/docs/audit-logging#audited_operations). While creating the sync in GCP, as part of the **Choose logs to include in sink** section you can use the following query:
+   ```sql
+   (resource.type=audited_resource and (resource.labels.service=bigtableadmin.googleapis.com or resource.labels.service=bigtable.googleapis.com))
+   ```
+
+  :::note
+  Bigtable audit logs use the service name **bigtableadmin.googleapis.com** for admin operations and **bigtable.googleapis.com** for data operations.
+  :::
+
+* Collect **Platform Logs** using [Google Cloud Platform source](/docs/send-data/hosted-collectors/google-source/google-cloud-platform-source). Bigtable platform logs include logs related to Bigtable instance, cluster, tables and backup. While creating the sync in GCP, as part of the **Choose logs to include in sink** section, you can use the following query:
+   ```sql
+   (resource.type=bigtable_instance or bigtable_cluster or bigtable_table or bigtable_backup)
+   ```
+
+### Configure metrics collection
+
+* Collect **GCP Metrics** using the [GCP Metric](/docs/send-data/hosted-collectors/google-source/gcp-metrics-source/) source. Note that in the Services dropdown, you'll need to select **Bigtable**. For Google Bigtable metrics and dimensions, refer to [Google Bigtable metrics](https://cloud.google.com/monitoring/api/metrics_gcp#gcp-bigtable).