vector source

Ingests data through another upstream Vector instance and outputs `log` and `metric` events.

The vector source is in beta. Please see the current enhancements and bugs for known issues. We kindly ask that you add any missing issues as it will help shape the roadmap of this component.

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

Config File

vector.toml (simple)
vector.toml (advanced)
type = "vector" # must be: "vector"
address = ""
# For a complete list of options see the "advanced" tab above.

How It Works

Delivery Guarantee

Due to the nature of this component, it offers a best effort delivery guarantee.


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.


The best place to start with troubleshooting is to check the Vector logs. This is typically located at /var/log/vector.log, then proceed to follow the Troubleshooting Guide.

If the Troubleshooting Guide does not resolve your issue, please:

  1. If encountered a bug, please file a bug report.

  2. If encountered a missing feature, please file a feature request.

  3. If you need help, join our chat/forum community. You can post a question and search previous questions.