tcp source

Ingests data through the TCP protocol and outputs `log` events.

The tcp source ingests data through the TCP protocol and outputs log events.

Config File

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


Given the following input line:

2019-02-13T19:48:34+00:00 [info] Started GET "/" for

A log event will be emitted with the following structure:

"timestamp": <timestamp> # current time,
"message": "2019-02-13T19:48:34+00:00 [info] Started GET "/" for",
"host": "" # current nostname

How It Works


By default, the tcp source will add context keys to your events via the host_key options.

Delivery Guarantee

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

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.

Line Delimiters

Each line is read until a new line delimiter (the 0xA byte) is found.


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. Check for any open tcp_source issues.

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

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

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