Stream Logs to GCP Cloud Storage

Netskope Log Streaming supports sending log files to GCP Cloud Storage. Provide details for the selected destination type. Destinations supported might offer different features and capabilities. The fields to fill in differ depending on the destination type the user selects.

For the GCP Cloud Storage destination field, fill in the following fields:

• Name of Destination:  A human-readable description for the destination.
• Bucket: The name of the storage bucket you created in your Google Cloud account. To learn more: Bucket naming conventions for Google Cloud Storage.
• Path: Optional. The path to the folder within your Google Cloud bucket where you want to store logs. In Google Cloud Storage, paths work as object names. When you enter a custom path, such as netskope/logs/{%Y}, Google Cloud Storage doesn’t create new Netskope, logs, and {%Y} folders in the bucket. Instead, the objects are stored in one bucket and named netskope/logs/{%Y}/filename. To learn more: Object naming guidelines for details.
• Private Key: The complete contents of the service account JSON key file generated and downloaded from your Google Cloud account. Paste the entire JSON object, including all fields such as type, project_id, private_key_id, private_key, client_email, and client_id. Do not paste only the private_key value — entering the standalone private key (PEM format) results in a credential validation error.

Example format:

{ “type”: “service_account”, “project_id”: “your-project-id”, “private_key_id”: “…”, “private_key”: “—–BEGIN PRIVATE KEY—–\n…\n—–END PRIVATE KEY—–\n”, “client_email”: “your-sa@your-project-id.iam.gserviceaccount.com”, “client_id”: “…”, … }

To create a service account key, see Create and delete service account keys in the Google Cloud documentation.