mirror of
https://github.com/falcosecurity/falco.git
synced 2025-07-31 22:16:49 +00:00
docs(falco.yaml): correct buffered_outputs
description
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
This commit is contained in:
parent
fa862b57e8
commit
a975e4cbc4
11
falco.yaml
11
falco.yaml
@ -549,9 +549,14 @@ json_include_tags_property: true
|
||||
|
||||
# [Stable] `buffered_outputs`
|
||||
#
|
||||
# Enabling buffering for the output queue can offer performance optimization,
|
||||
# efficient resource usage, and smoother data flow, resulting in a more reliable
|
||||
# output mechanism. By default, buffering is disabled (false).
|
||||
# Global buffering option for output channels. When disabled, the output channel
|
||||
# that supports buffering flushes the output buffer on every alert. This can lead to
|
||||
# increased CPU usage but is useful when piping outputs to another process or script.
|
||||
# Buffering is currently supported by `file_output`, `program_output`, and `std_output`.
|
||||
# Some output channels may implement buffering strategies you cannot control.
|
||||
# Additionally, this setting is separate from the `output_queue` option. The output queue
|
||||
# sits between the rule engine and the output channels, while output buffering occurs
|
||||
# afterward once the specific channel implementation outputs the formatted message.
|
||||
buffered_outputs: false
|
||||
|
||||
# [Incubating] `rule_matching`
|
||||
|
Loading…
Reference in New Issue
Block a user