Use Observability Pipelines’ Google Pub/Sub source to pull logs from the Google Cloud Pub/Sub messaging system. Select and set up this source when you set up a pipeline.

Prerequisites

To use Observability Pipelines’ Google Pub/Sub source, you need the following information available:

• The Google Pub/Sub source requires a Pub/Sub subscription.
• A Google Developer Service Account Credential to authenticate the Observability Pipelines Worker. Contact your Google Security Operations representative for a Google Developer Service Account Credential. This credential is a JSON file and must be placed under DD_OP_DATA_DIR/config. See Getting API authentication credentials for more information.

Set up the source in the pipeline UI

Select and set up this source when you set up a pipeline. The information below is for the source settings in the pipeline UI.

1. Enter the name of the source project.
2. Enter the path to the Google Developer Service Account Credential JSON file. See Prerequisites for more information.
3. Enter the subscription name.
4. Select the decoder you want to use (Bytes, GELF, JSON, syslog).
5. Optionally, toggle the switch to enable TLS. If you enable TLS, the following certificate and key files are required.
   Note: All file paths are made relative to the configuration data directory, which is /var/lib/observability-pipelines-worker/config/ by default. See Advanced Configurations for more information. The file must be owned by the observability-pipelines-worker group and observability-pipelines-worker user, or at least readable by the group or user.
   • Server Certificate Path: The path to the certificate file that has been signed by your Certificate Authority (CA) Root File in DER or PEM (X.509).
   • CA Certificate Path: The path to the certificate file that is your Certificate Authority (CA) Root File in DER or PEM (X.509).
   • Private Key Path: The path to the .key private key file that belongs to your Server Certificate Path in DER or PEM (PKCS #8) format.