Google Cloud Pub/Sub
The Google Cloud Pub/Sub integration enables Litmus Edge (LE) to connect to Google Cloud Pub/Sub for publishing and receiving messages.
Supported communication
- Outbound (Publish data from Edge to Google Cloud Pub/Sub) - Yes
- Inbound (Subscribe data from Google Cloud Pub/Sub to Edge) - Yes
Configurations
Field | Details | Required |
|---|---|---|
Name | Connector name. | Yes |
Credentials (.json) | Service account credentials JSON. | Yes |
Project ID | The project ID of the cloud project. | Yes |
Private Key ID | Optional override for the private_key_id field inside the credentials JSON. | No |
Client Email | Optional override for the client_email field inside the credentials JSON. | No |
Default Topic | Default Pub/Sub topic. Accepts a bare topic name or the fully-qualified path projects/{project}/topics/{topic}. | Yes |
Custom Attributes | Static attributes attached to every published message. | No |
Parallel Publish Count | Number of messages published in parallel. Higher values increase throughput and resource usage. | Yes |
Ack deadline (seconds) | Ack deadline applied to subscriptions created by this connector. | No |
Publish byte threshold | Publisher batch size in bytes. | No |
Publish count threshold | Publisher batch size in message count. | No |
Publish delay threshold (milliseconds) | Maximum time the publisher waits before flushing a partial batch. | No |
Connect timeout (seconds) | Timeout for establishing a new client connection to Pub/Sub. | No |
Throttling limit | Set a limit on the number of outbound messages per second. If sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost. | No |
Persistent storage configurations
Field | Details | Required |
|---|---|---|
Persistent storage | If enabled, messages in the outbound queue are stored on disk. If there are interruptions in connection or power loss, messages are retained and eventually sent when the connection is restored. | No |
Persistent storage size limit | Set the size limit for storing persisted data in GB. | No |
Queue mode | Select the sequence of data transfer: FIFO or LIFO. Selecting FIFO (First In First Out) sends the earliest message first. Selecting LIFO (Last In First Out) sends the latest message first. | No |