Vector is a simple beast to tame, in this guide we'll send an event through it and touch on some basic concepts.
If you haven't already, install Vector. Here's a script for the lazy:curl --proto '=https' --tlsv1.2 -sSf https://sh.vector.dev | shexplain this command
Configure itvector.toml[sources.foo]type = "stdin"[sinks.bar]inputs = ["foo"]type = "console"encoding.codec = "text"explain this command
Every component within a Vector config has an identifier chosen by you. This allows you to specify where a sink should gather its data from (using the
That's it for our first config, now pipe an event through it:echo 'Hello World!' | vector --config ./vector.tomlexplain this command
Your input event will get echoed back (along with some service logs) unchanged:... some logs ...Hello World!
That's because the raw input text of our source was captured internally within the field
message, and the
encoding.codecoption of our sink prints the raw contents of
If you expected something more interesting to happen then that's on you. The text came out unchanged because we didn't ask Vector to change it, we can remedy that by following the next guide in the series.