diff --git a/modules/cluster-logging-collector-legacy-fluentd.adoc b/modules/cluster-logging-collector-legacy-fluentd.adoc index ac20691c2945..89d6a7de78ab 100644 --- a/modules/cluster-logging-collector-legacy-fluentd.adoc +++ b/modules/cluster-logging-collector-legacy-fluentd.adoc @@ -25,7 +25,7 @@ To send logs using the Fluentd *forward* protocol, create a configuration file c @type forward - self_hostname fluentd.example.com + self_hostname ${hostname} shared_key "fluent-receiver" transport tls @@ -61,13 +61,13 @@ To configure {product-title} to forward logs using the legacy Fluentd method: @type forward - self_hostname <1> - shared_key <2> + self_hostname ${hostname} + shared_key <1> - transport tls <3> - tls_verify_hostname <4> - tls_cert_path <5> - <6> + transport tls <2> + tls_verify_hostname <3> + tls_cert_path <4> + <5> @type file path '/var/lib/fluentd/secureforwardlegacy' queued_chunks_limit_size "#{ENV['BUFFER_QUEUE_LIMIT'] || '1024' }" @@ -80,27 +80,26 @@ To configure {product-title} to forward logs using the legacy Fluentd method: overflow_action "#{ENV['BUFFER_QUEUE_FULL_ACTION'] || 'exception'}" - name <7> - host <8> - hostlabel <9> - port <10> + name <6> + host <7> + hostlabel <8> + port <9> - <11> + <10> name host ---- -<1> Specify the default value of the auto-generated certificate common name (CN). -<2> Enter the shared key between nodes -<3> Specify `tls` to enable TLS validation. -<4> Set to `true` to verify the server cert hostname. Set to `false` to ignore server cert hostname. -<5> Specify the path to the private CA certificate file as `/etc/ocp-forward/ca_cert.pem`. -<6> Specify the link:https://docs.fluentd.org/configuration/buffer-section[Fluentd buffer parameters] as needed. -<7> Optionally, enter a name for this server. -<8> Specify the host name or IP of the server. -<9> Specify the host label of the server. -<10> Specify the port of the server. -<11> Optionally, add additional servers. +<1> Enter the shared key between nodes. +<2> Specify `tls` to enable TLS validation. +<3> Set to `true` to verify the server cert host name. Set to `false` to ignore server cert host name. +<4> Specify the path to the private CA certificate file as `/etc/ocp-forward/ca_cert.pem`. +<5> Specify the link:https://docs.fluentd.org/configuration/buffer-section[Fluentd buffer parameters] as needed. +<6> Optionally, enter a name for this server. +<7> Specify the host name or IP of the server. +<8> Specify the host label of the server. +<9> Specify the port of the server. +<10> Optionally, add additional servers. If you specify two or more servers, *forward* uses these server nodes in a round-robin order. + To use Mutual TLS (mTLS) authentication, see the link:https://docs.fluentd.org/output/forward#tips-and-tricks[Fluentd documentation] for information about client certificate, key parameters, and other settings. @@ -112,8 +111,7 @@ To use Mutual TLS (mTLS) authentication, see the link:https://docs.fluentd.org/o $ oc create configmap secure-forward --from-file=secure-forward.conf -n openshift-logging ---- -The Cluster Logging Operator redeploys the Fluentd pods. If the pods do not redeploy, you can delete the Fluentd -pods to force them to redeploy. +The Cluster Logging Operator redeploys the Fluentd pods. If the pods do not redeploy, you can delete the Fluentd pods to force them to redeploy. [source,terminal] ----