secure_forward
Last updated
Was this helpful?
Last updated
Was this helpful?
The out_secure_forward output plugin sends messages via SSL with authentication (cf. ). This document doesn't describe all parameters. If you want to know full features, check the Further Reading section.
This section provides some example configurations for out_secure_forward.
At first, generate private CA file on side of input plugin by secure-forward-ca-generate, then copy that file to output plugin side by safe way (scp, or anyway else).
Without hostname ACL (not yet implemented), `self_hostname` is not checked in any state. The `"#{Socket.gethostname}"` placeholder is available for such cases.
When two or more <server>...</server> clauses are specified, out_secure_forward uses these server nodes in a round-robin order. The servers with standby yes are NOT selected until all non-standby servers go down.
If a server requires username & password, set `username` and `password` in the `` section:
Use the keepalive parameter to specify keepalive timeouts. For example, the configuration below disconnects and re-connects its SSL connection every hour. By default, keepalive is set to 0 and the connection does NOT get disconnected unless there is a connection issue (This feature is for DNS name updates and refreshing SSL common keys).
Example to send and receive several different kinds of logs (format is set to none for simplicity here).
This parameter is required. Its value must be secure_forward.
The default value is 24284.
The default value is 0.0.0.0.
Indicate published connection is secure or not. Specify yes (or true) if secure encryption needed.
The file path of private CA certificate file. This file must be shared with input plugin. The default is blank, but this parameter must be specified except for the case to use certificates signed by public CA.
Default value of the auto-generated certificate common name (CN).
Shared key between nodes..
The duration for keepalive. If this parameter is not specified, keepalive is disabled.
The send timeout value for sockets. The default value is 60 seconds.
The interval between SSL reconnects. The default value is 5 seconds.
The number of bytes read per nonblocking read. The default value is 8MB=810241024 bytes.
The interval between the non-blocking reads, in milliseconds. The default value is 50.
The interval between SSL reconnects in milliseconds. The default value is 200.
For advanced usage, you can tune Fluentd's internal buffering mechanism with these parameters.
The interval between data flushes. The default is 60s. The suffixes "s" (seconds), "m" (minutes), and "h" (hours) can be used.
If set to true, Fluentd waits for the buffer to flush at shutdown. By default, it is set to true for Memory Buffer and false for File Buffer.
The initial and maximum intervals between write retries. The default values are 1.0 seconds and unset (no limit). The interval doubles (with +/-12.5% randomness) every retry until max_retry_wait is reached.
Since td-agent will retry 17 times before giving up by default (see the retry_limit parameter for details), the sleep interval can be up to approximately 131072 seconds (roughly 36 hours) in the default configurations.
The limit on the number of retries before buffered data is discarded, and an option to disable that limit (if true, the value of retry_limit is ignored and there is no limit). The default values are 17 and false (not disabled). If the limit is reached, buffered data is discarded and the retry interval is reset to its initial value (retry_wait).
The number of threads to flush the buffer. This option can be used to parallelize writes into the output(s) designated by the output plugin. Increasing the number of threads improves the flush throughput to hide write / network latency. The default is 1.
The threshold for checking chunk flush performance. The default value is 20.0 seconds. Note that parameter type is float, not time.
If chunk flush takes longer time than this threshold, fluentd logs warning message like below:
The log_level option allows the user to set different levels of logging for each plugin. The supported log levels are: fatal, error, warn, info, debug, and trace.
out_secure_forward is not included in either td-agent package or fluentd gem. In order to install it, please refer to the article.
The buffer type is memory by default () for the ease of testing, however file () buffer type is always recommended for the production deployments. If you use file buffer type, buffer_path parameter is required.
The length of the chunk queue and the size of each chunk, respectively. Please see the article for the basic buffer structure. The default values are 64 and 8m, respectively. The suffixes "k" (KB), "m" (MB), and "g" (GB) can be used for buffer_chunk_limit.
Please see the for further details.
If this article is incorrect or outdated, or omits critical information, please . is a open source project under . All components are available under the Apache 2 License.
