Skip to content

[enterprise-4.7] RHDEVDOCS-2603 #29992

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 2, 2021
Merged

[enterprise-4.7] RHDEVDOCS-2603 #29992

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 23 additions & 25 deletions modules/cluster-logging-collector-legacy-fluentd.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ To send logs using the Fluentd *forward* protocol, create a configuration file c
<store>
@type forward
<security>
self_hostname fluentd.example.com
self_hostname ${hostname}
shared_key "fluent-receiver"
</security>
transport tls
Expand Down Expand Up @@ -61,13 +61,13 @@ To configure {product-title} to forward logs using the legacy Fluentd method:
<store>
@type forward
<security>
self_hostname <common-name> <1>
shared_key <key> <2>
self_hostname ${hostname}
shared_key <key> <1>
</security>
transport tls <3>
tls_verify_hostname <value> <4>
tls_cert_path <path_to_file> <5>
<buffer> <6>
transport tls <2>
tls_verify_hostname <value> <3>
tls_cert_path <path_to_file> <4>
<buffer> <5>
@type file
path '/var/lib/fluentd/secureforwardlegacy'
queued_chunks_limit_size "#{ENV['BUFFER_QUEUE_LIMIT'] || '1024' }"
Expand All @@ -80,27 +80,26 @@ To configure {product-title} to forward logs using the legacy Fluentd method:
overflow_action "#{ENV['BUFFER_QUEUE_FULL_ACTION'] || 'exception'}"
</buffer>
<server>
name <7>
host <8>
hostlabel <9>
port <10>
name <6>
host <7>
hostlabel <8>
port <9>
</server>
<server> <11>
<server> <10>
name
host
</server>
----
<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.
Expand All @@ -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]
----
Expand Down