The glossary contains common terms and their definitions.
"Batch" refers to a batched payload within a sink. It is a batch of events encoded into a payload that the downstream service understands.
"Benchmark" refers to a test designed to measure performance and resource usage. You can learn more about Vector's benchmarks in the Benchmarks section.
"Binary" refers to the static binary that Vector compiles to.
"Buffer" refers to an ordered queue of events that is coupled with a sink.
"Configuration" refers to the settings and options used to control Vector's behavior. You can learn more about Vector's configuration in the Configuration section.
"Durability" refers to the ability to retain data across exceptional events. In the context of Vector, this typically refers to the ability to retain data across restarts.
"Event" refers to a single unit of data that flows through Vector. You can learn more about events in the Data Model section.
"Filter" refers to a type of transform that filters events or fields on an event.
"flush" refers to the act of sending a batched payload to a downstream service. It is commonly used in conjunction with "buffer".
"Github"" refers to the service used to host Vector's source code.
"Guide" is a tutorial or walk through on a specific subject. You can see Vector's guides in the Guides section.
"Log" refers to an individual log event. This is a type of Vector event.
A sporty Italian that bleeds Rust, is a core member of the Vector team, and who does not approve of New York pizza.
"Metric" refers to an individual data unit used to represent a point in time measurement. This is a type of Vector event.
"Parser" refers to a transform that parses event data.
"Pipeline" refers to the end result of deploying Vector into your infrastructure. A piepline may be one or more Vector instances that ultimately get your data from A to B.
"Reducer" refers to a transform that reduces data into a metric.
"Repo" refers to a Git repository, usually the Vector Git repository.
"Roles" refers to a deployment role under which Vector is deployed.
"Router" refers is something that accepts and routes data to many destinations, this is commonly used to describe Vector.
"Rust" refers to the Rust programming language that Vector is written in.
"Sampler" refers to a transform that samples data.
"Sink" refers to the Vector sink concept.
"Source" refers to the Vector source concept.
"Structured log" refers to a log represented in a structured form, such as a map. This is different from a text log, which is represented as a single text string.
"Table" refers to the TOML table type.
"TOML" refers to Tom's Obvious Markup Language and it is the syntax used to represent the Vector configuration.
"Topology" refers to a directed acyclic graph of components that is created when you configure Vector.
"Transform" refers to the Vector transform concept.
"Use case" refers to a way in which Vector is used, such logs, metrics, reducing cost, etc.
"Vector" is the name of this project.