vector sink
The vector
sink streams log
events to another downstream vector
source.
Configuration
- Common
- Advanced
[sinks.my_sink_id]type = "vector" # example, must be: "vector"inputs = ["my-source-id"] # exampleaddress = "92.12.333.224:5000" # example
Options
address
The downstream Vector address.
buffer
Configures the sink specific buffer.
max_size
The maximum size of the buffer on the disk.
type
The buffer's type / location. disk
buffers are persistent and will be retained between restarts.
"memory"
"memory"
"disk"
when_full
The behavior when the buffer becomes full.
"block"
"block"
"drop_newest"
healthcheck
Enables/disables the sink healthcheck upon start. See Health Checks for more info.
true
Output
The vector
sink streams log
events to another downstream vector
source.
How It Works
Environment Variables
Environment variables are supported through all of Vector's configuration.
Simply add ${MY_ENV_VAR}
in your Vector configuration file and the variable
will be replaced before being evaluated.
You can learn more in the Environment Variables section.
Health Checks
Health checks ensure that the downstream service is accessible and ready to accept data. This check is performed upon sink initialization. If the health check fails an error will be logged and Vector will proceed to start.
Require Health Checks
If you'd like to exit immediately upon a health check failure, you can
pass the --require-healthy
flag:
vector --config /etc/vector/vector.toml --require-healthy
Disable Health Checks
If you'd like to disable health checks for this sink you can set thehealthcheck
option to false
.
Streaming
The vector
sink streams data on a real-time
event-by-event basis. It does not batch data.