Google Cloud Logging Connector
This guide covers implementing Descope's Google Cloud Logging connector. Google Cloud Logging is a troubleshooting product that allows you to collect log analytics.
Descope enables you to automatically collect logs and audit events and stream them to a Google Cloud Logging account.
Configure Google Cloud Logging connector
Navigate to the Connectors page in the Descope Console and select Google Cloud Logging to create a new Google Cloud Logging connector.
The following parameters are required to use it:
- Connector Name: Provide a unique name for your connector. This assists in distinguishing it, especially when multiple connectors are derived from the same template.
- Connector Description: Briefly explain the purpose of this connector.
- Service Account Key: A Service Account Key JSON file created from a service account on your Google Cloud project. This file is used to authenticate and authorize the connector to access Google Cloud Logging. The service account this key belongs to must have the appropriate permissions to write logs.(e.g. Logs Writer).
- Stream Audit Events: Select which events are sent to Google Cloud Logging. Descopers can allow all audit events or filter them based on certain actions that occur or tenants in the project.
- Stream Troubleshooting Events: Decide whether troubleshooting events are also sent to Google Cloud Logging.
Getting the Service Account Key
Follow the steps in the Google Cloud docs to create a Service Account Key.
Viewing Audit Logs
Once you've completed all of the steps above, your Descope Audit Logs should now available in Google Cloud Logging. You can test the connector during configuration to verify that logs are being sent and collected correctly.
The logs can still be viewed in Descope on the Audit and Troubleshoot page of the Descope Console.