Topology Model

Vector's topology model is based on a directed acyclic graph of components that contains independent subgraphs. Events must flow in a single direction from sources to sinks, and cannot create cycles. Each component in the graph can produce zero or more events.

Defining topologies

A Vector topology is defined through a TOML, YAML, or JSON configuration file. For maintainability, many Vector users use data templating languages like Jsonnet or Cue.

Configuration is checked during compile-time (Vector boot) to present simple mistakes and enforce the DAG properties.

In-flight manipulation

Vector's topology can be adjusted in real-time without restarting Vector.

Reload

Vector supports hot reloading to apply any configuration changes. This is achieved by sending a SIGHUP process signal to Vector's process.

API

Vector also includes an API that allows for real-time observation and manipulation of a running Vector instance.