Google Cloud Pub/Sub Integration Guide
Review the following guide for setting up an integration between Litmus Edge and Google Pub/Sub service.
Once the integration is set up, you can use it for the following:
- Publishing data from a topic in your edge device to a Subscription topic in the Google Cloud Platform (GCP)
- Subscribing to data published by a Publication topic in the Google Cloud Platform
- You need to create a Google Service Account. Make sure the account has the correct roles and permissions required for setting up the connection.
- Refer to the following Google resources for learning more about Pub/Sub and configuring connections:
- Configure Private Google Access for on-premises hosts > Domain Options (information regarding private access to GCP services)
- Supported products and limitations > Pub/Sub (information regarding private access to GCP services)
Follow the steps below to set up the outbound connection.
In the Google Cloud Platform, create a publication topic. A matching subscription topic is created automatically, with the -sub suffix appended to the topic name.
Follow the steps to Add a Connector and select the Google Cloud Pub/Sub Connector provider.
For more information about message publication settings, see the SDK on Publish Settings.
Configure the following parameters.
- Name: Enter a name for the connector.
- Service Account Key (.json): Copy or save the JSON key from your Google Cloud Platform and paste or upload it here.
- The project ID of the cloud project: Copy the ID from your Google Cloud Platform and paste it here.
- The private key ID of the cloud project: Copy the key ID from your Google Cloud Platform and paste it here.
- The client email of the cloud project: Enter the email from your Google Cloud Platform.
- Integration Topic: Copy the name of the Publication topic (without the "-sub" suffix) from your Google Cloud Platform and paste it here.
- Custom Attributes: You can add custom attributes in key/value pairs for further data processing. Refer to the following to learn more:
- Parallel Publish Count: The number of messages being published simultaneously. The default value is 100.
- Parallel byte threshold: The minimum size of a batch (in bytes) for the batch to be published. The default value is zero, which means that there is no threshold (limit).
- Publish count threshold: The minimum number of messages in a batch for the batch to be published. The default value is zero, which means that there is no threshold (limit).
- Publish delay threshold (Milliseconds): The maximum time that the client will attempt to publish a batch of messages. The default value is zero, which means that there is no threshold (limit).
- Throttling limit: The maximum number of messages per second to be processed. The default value is zero, which means that there is no limit.
- Persistent storage: When enabled, this will cause messages to undergo a store-and-forward procedure. Messages will be stored within Litmus Edge when cloud providers are online.
- Queue Mode: Select the queue mode as lifo (last in first out) or fifo (first in first out). Selecting lifo means that the last data entry is processed first, and selecting fifo means the first data entry is processed first.
After adding the connector, click the toggle in the connector tile to enable it.
If you see a Failed status, you can review the Connector Logs and relevant error messages.
You will now need to import the tags you added in Step 2 to the connector as topics.
After importing the tag(s), do the following:
- Edit the tag and configure the Remote Data Topic. Copy and paste the name of the Subscription topic (with the -sub suffix) from your Google Cloud Platform.
- Make sure the connector has a CONNECTED status.
Because you imported DeviceHub tags for a CONNECTED connector, all topics will be disabled.
To enable the topics, return to the Topics tab and click the Enable all topics icon.
To verify the connection in Google Cloud Platform:
Pull the subscription topic to see messages it receives from the Litmus Edge outbound topics created previously.
List of Litmus Edge outbound topicsView the subscription statistics.
Graph of subscription statistic
Follow the steps below to set up the inbound connection.
See Publish messages to topics to learn more about publishing messages in Google Pub/Sub.
In the Google Cloud Platform, create a publication topic.
Follow the steps to Add a Connector and select the Google Cloud Pub/Sub Connector provider.
Configure the following parameters.
- Name: Enter a name for the connector.
- Service Account Key (.json): Copy or save the JSON key from your Google Cloud Platform and paste or upload it here.
- The project ID of the cloud project: Copy the ID from your Google Cloud Platform and paste it here.
- The private key ID of the cloud project: Copy the key ID from your Google Cloud Platform and paste it here.
- The client email of the cloud project: Enter the email from your Google Cloud Platform.
- Integration Topic: Copy the name of the Publication topic (without the "-sub" suffix) from your Google Cloud Platform and paste it here.
- Custom Attributes: You can add custom attributes in key/value pairs for further data processing. Refer to the following to learn more:
- Parallel Publish Count: The number of messages being published simultaneously. The default value is 100.
- Parallel byte threshold: The minimum size of a batch (in bytes) for the batch to be published. The default value is zero, which means that there is no threshold (limit).
- Publish count threshold: The minimum number of messages in a batch for the batch to be published. The default value is zero, which means that there is no threshold (limit).
- Publish delay threshold (Milliseconds): The maximum time that the client will attempt to publish a batch of messages. The default value is zero, which means that there is no threshold (limit).
- Throttling limit: The maximum number of messages per second to be processed. The default value is zero, which means that there is no limit.
- Persistent storage: When enabled, this will cause messages to undergo a store-and-forward procedure. Messages will be stored within Litmus Edge when cloud providers are online.
- Queue Mode: Select the queue mode as lifo (last in first out) or fifo (first in first out). Selecting lifo means that the last data entry is processed first, and selecting fifo means the first data entry is processed first.
After adding the connector, click the toggle in the connector tile to enable it.
If you see a Failed status, you can review the Connector Logs and relevant error messages.
You will now need to create a topic in Litmus Edge from the Google Cloud Platform publication topic created in Step 1.
To create inbound topics:
- Navigate to Integration.
- Click the connector tile.
- Click the Topics tab.
Click the Add a new subscription icon. The Data Integration dialog box appears.
- Configure the following parameters.
- Data Direction: Select Remote to Local - Inbound.
- Local Data Topic: Enter a name for the topic name in Litmus Edge.
- Remote Data Topic: Copy and paste the Publication topic from your Google Cloud Platform.
- Enable: Select the toggle to enable the topic.
- Click Yes to add the topic.
- From the connector tile, ensure the connector is not disabled and still shows a CONNECTED status. Also verify the topic shows an Enabled status.
Start sending messages through the publication topic (created in Step 1) from the Google Cloud Platform. See Publish messages to topics to learn more.
You can do one of the following to verify the connection in Litmus Edge. When configuring the Flow or application, use the the Local Data Topic name configured in Step 4.