Vector Source

The Vector vector source ingests data through another upstream vector sink and outputs log and metric events.

Configuration

vector.toml

[sources.my_source_id]
  # REQUIRED
  type = "vector" # must be: "vector"
  address = "0.0.0.0:9000" # example

  # OPTIONAL
  shutdown_timeout_secs = 30 # default, seconds

Options

2 items

common onlyrequired only

stringcommonrequired

address

The TCP address to listen for connections on, or `systemd#N to use the Nth socket passed by systemd socket activation. If an address is used it must include a port.

No default

View examples

int (seconds)commonrequired

shutdown_timeout_secs

The timeout before a connection is forcefully closed during shutdown.

Default: 30 (seconds)

View examples

Output

The vector source is a pass-through source and is intended to accept data from an upstream vector sink. Datta is not changed or augmented.

How It Works

Encoding

Data is encoded via Vector's event protobuf before it is sent over the wire.

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.

Message Acking

Currently, Vector does not perform any application level message acknowledgement. While rare, this means the individual message could be lost.

TCP Protocol

Upstream Vector instances forward data to downstream Vector instances via the TCP protocol.