Starting

Starting Vector

Vector can be started by calling the vector binary directly, no command is necessary.

Manual
Systemd
Initd
Homebrew
vector --config /etc/vector/vector.toml
sudo systemctl start vector
/etc/init.d/vector start
brew services start vector

Flags

Flag

Description

Required

-c, --config <path>

Path the Vector configuration file.

Optional

-d, --dry-run

Vector will validate configuration and exit.

-q, --quiet

Raises the log level to warn.

-qq

Raises the log level to error, the highest level possible.

-r, --require-healthy

Causes vector to immediately exit if any sinks fail their healthchecks.

-t, --threads

Limits the number of internal threads Vector can spawn. See the Limiting Resources in the Agent role documentation.

-v, --verbose

Drops the log level to debug.

-vv

Drops the log level to trace, the lowest level possible.

Daemonizing

Vector does not directly offer a way to daemonize the Vector process. We highly recommend that you use a utility like Systemd to daemonize and manage your processes. Vector provides a vector.service file for Systemd.

Exit Codes

If Vector fails to start it will exit with one of the preferred exit codes as defined by sysexits.h. A full list of exit codes can be found in the exitcodes Rust crate. The relevant codes that Vector uses are:

Code

Description

0

No error.

78

Bad configuration.