Azure Monitor Logs
Publish log events to the Azure Monitor Logs service
type = "memory"
type = "disk"
|Stores the sink’s buffer on disk. This is less performant, but durable. Data will not be lost between restarts. Will also hold data in memory to enhance performance. WARNING: This may stall the sink if disk performance isn’t on par with the throughput. For comparison, AWS gp2 volumes are usually too slow for common cases.|
|Stores the sink’s buffer in memory. This is more performant, but less durable. Data will be lost if Vector is restarted forcefully.|
|Applies back pressure when the buffer is full. This prevents data loss, but will cause data to pile up on the edge.|
|Drops new data as it’s received. This data is lost. This should be used when performance is the highest priority.|
|Formats as a RFC3339 string|
|Formats as a unix timestamp|
See configuration for more info.
key_filemust also be set.
crt_filemust also be set.
true(the default), Vector will validate the TLS certificate of the remote host.
true(the default), Vector will validate the configured remote host name against the remote host’s TLS certificate. Do NOT set this to
falseunless you understand the risks of not verifying the remote hostname.
This component buffers & batches data as shown in the diagram above. You’ll notice that Vector treats these concepts differently, instead of treating them as global concepts, Vector treats them as sink specific concepts. This isolates sinks, ensuring services disruptions are contained and delivery guarantees are honored.
Batches are flushed when 1 of 2 conditions are met:
- The batch age meets or exceeds the configured
- The batch size meets or exceeds the configured
Buffers are controlled via the
If you’d like to exit immediately upon a health check failure, you can pass the
vector --config /etc/vector/vector.toml --require-healthy