Vector can be installed through Homebrew which is generally used on MacOS systems.
The daemon deployment strategy is designed for data
collection on a single host. Vector runs in the background, in its own process,
collecting all data for that host.
Typically data is collected from a process manager, such as Journald via
journald source, but can be collected
through any of Vector's sources.
The following diagram demonstrates how it works.
Add the Timber tap and install
vectorbrew tap timberio/brew && brew install vector
Configure Vectorecho '[sources.in]type = "file" # requiredinclude = ["/var/log/nginx/*.log"] # required[sinks.out]# Generaltype = "console" # requiredinputs = ["in"] # required# Encodingencoding.codec = "json" # required' > /etc/vector/vector.tomlexplain this command
Start Vectorbrew services start vector
The Vector configuration file is placed in:
A full spec is located at
/usr/local/etc/vector/vector.spec.toml and examples
are located in
/usr/local/etc/vector/examples/*. You can learn more about
configuring Vector in the Configuration section.
How you deploy Vector is largely dependent on your use case and environment. Please see the deployment section for more info on how to deploy Vector.
Vector can be managed through the Homebrew services manager:
brew remove vector
brew update && brew upgrade vector
Vector's Homebrew packages only support the X86_64 arhcitecture.
Historical Vector versions can be found in the releases. Once you've found the version you'd like to install you can specify it with:
brew install vector@X.X.X
Due to limitations of Homebrew, Vector cannot pin specific major or minor versions. If this is a requirement, then we recommend installing Vector directly from an archive.
Vector's Homebrew source files are located in Vector's brew repo.