GCP PubSub Sink

The Vector gcp_pubsub sink batches log events to Google Cloud Platform's Pubsub service via the REST Interface.

Configuration

• Common
• Advanced

vector.toml

[sinks.my_sink_id]
  type = "gcp_pubsub" # must be: "gcp_pubsub"
  inputs = ["my-source-id"] # example
  project = "vector-123456" # example
  topic = "this-is-a-topic" # example

Options

9 items

common onlyrequired only

stringoptional

api_key

A Google Cloud API key used to authenticate access the pubsub project and topic. Either this or credentials_path must be set.

tableoptional

batch

Configures the sink batching behavior.

intbytesoptional

max_size

The maximum size of a batch before it is flushed. See Buffers & Batches for more info.

Default: 10485760

View examples

intsecondsoptional

timeout_secs

The maximum age of a batch before it is flushed. See Buffers & Batches for more info.

Default: 1

View examples

tableoptional

buffer

Configures the sink buffer behavior.

inteventsoptional

max_events

The maximum number of events allowed in the buffer.

Default: 500

Only relevant when: type = "memory"

View examples

intbytesoptional

max_size

The maximum size of the buffer on the disk. See Buffers & Batches for more info.

No default

Only relevant when: type = "disk"

View examples

stringenumoptional

type

The buffer's type / location. disk buffers are persistent and will be retained between restarts.

Default: "memory"

Enum, must be one of: "memory" "disk"

View examples

stringenumoptional

when_full

The behavior when the buffer becomes full.

Default: "block"

Enum, must be one of: "block" "drop_newest"

View examples

stringoptional

credentials_path

The filename for a Google Cloud service account credentials JSON file used to authenticate access to the pubsub project and topic. Either this or api_key must be set.

booloptional

healthcheck

Enables/disables the sink healthcheck upon start. See Health Checks for more info.

Default: true

View examples

commonstringrequired

project

The project name to which to publish logs.

No default

View examples

tableoptional

request

Configures the sink request behavior.

intoptional

in_flight_limit

The maximum number of in-flight requests allowed at any given time. See Rate Limits for more info.

Default: 5

View examples

intsecondsoptional

rate_limit_duration_secs

The window used for the rate_limit_num option See Rate Limits for more info.

Default: 1

View examples

intoptional

rate_limit_num

The maximum number of requests allowed within the rate_limit_duration_secs window. See Rate Limits for more info.

Default: 100

View examples

intoptional

retry_attempts

The maximum number of retries to make for failed requests. See Retry Policy for more info.

Default: 9223372036854776000

View examples

intsecondsoptional

retry_initial_backoff_secs

The amount of time to wait before attempting the first retry for a failed request. Once, the first retry has failed the fibonacci sequence will be used to select future backoffs.

Default: 1

View examples

intsecondsoptional

retry_max_duration_secs

The maximum amount of time to wait between retries.

Default: 10

View examples

intsecondsoptional

timeout_secs

The maximum time a request can take before being aborted. It is highly recommended that you do not lower value below the service's internal timeout, as this could create orphaned requests, pile on retries, and result in deuplicate data downstream. See Buffers & Batches for more info.

Default: 60

View examples

tableoptional

tls

Configures the TLS options for connections from this sink.

stringoptional

ca_path

Absolute path to an additional CA certificate file, in DER or PEM format (X.509).

No default

View examples

stringoptional

crt_path

Absolute path to a certificate file used to identify this connection, in DER or PEM format (X.509) or PKCS#12. If this is set and is not a PKCS#12 archive, key_path must also be set.

No default

View examples

stringoptional

key_pass

Pass phrase used to unlock the encrypted key file. This has no effect unless key_pass above is set.

No default

View examples

stringoptional

key_path

Absolute path to a certificate key file used to identify this connection, in DER or PEM format (PKCS#8). If this is set, crt_path must also be set.

No default

View examples

booloptional

verify_certificate

If true (the default), Vector will validate the TLS certificate of the remote host. Do NOT set this to false unless you understand the risks of not verifying the remote certificate.

Default: true

View examples

booloptional

verify_hostname

If true (the default), Vector will validate the configured remote host name against the remote host's TLS certificate. Do NOT set this to false unless you understand the risks of not verifying the remote hostname.

Default: true

View examples

commonstringrequired

topic

The topic within the project to which to publish logs.

No default

View examples

How It Works

Buffers & Batches

The gcp_pubsub sink buffers & batches data as shown in the diagram above. You'll notice that Vector treats these concepts differently, instead of treating them as global concepts, Vector treats them as sink specific concepts. This isolates sinks, ensuring services disruptions are contained and delivery guarantees are honored.

Batches are flushed when 1 of 2 conditions are met:

1. The batch age meets or exceeds the configured timeout_secs.
2. The batch size meets or exceeds the configured max_size.

Buffers are controlled via the buffer.* options.

Environment Variables

Environment variables are supported through all of Vector's configuration. Simply add ${MY_ENV_VAR} in your Vector configuration file and the variable will be replaced before being evaluated.

You can learn more in the Environment Variables section.

Health Checks

Health checks ensure that the downstream service is accessible and ready to accept data. This check is performed upon sink initialization. If the health check fails an error will be logged and Vector will proceed to start.

Require Health Checks

If you'd like to exit immediately upon a health check failure, you can pass the --require-healthy flag:

vector --config /etc/vector/vector.toml --require-healthy

Disable Health Checks

If you'd like to disable health checks for this sink you can set the healthcheck option to false.

Rate Limits

Vector offers a few levers to control the rate and volume of requests to the downstream service. Start with the rate_limit_duration_secs and rate_limit_num options to ensure Vector does not exceed the specified number of requests in the specified window. You can further control the pace at which this window is saturated with the in_flight_limit option, which will guarantee no more than the specified number of requests are in-flight at any given time.

Please note, Vector's defaults are carefully chosen and it should be rare that you need to adjust these. If you found a good reason to do so please share it with the Vector team by opening an issie.

Retry Policy

Vector will retry failed requests (status == 429, >= 500, and != 501). Other responses will not be retried. You can control the number of retry attempts and backoff rate with the retry_attempts and retry_backoff_secs options.