Skip to content

Commit 9d8b21a

Browse files
committed
fix merge error
1 parent f51e7e4 commit 9d8b21a

File tree

2 files changed

+6
-1
lines changed

2 files changed

+6
-1
lines changed

logging/cluster-logging-external.adoc

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,6 @@ You cannot use the ConfigMap methods and the Log Forwarding API in the same clus
2929
// modules required to cover the user story. You can also include other
3030
// assemblies.
3131

32-
3332
include::modules/cluster-logging-collector-log-forwarding-about.adoc[leveloffset=+1]
3433
include::modules/cluster-logging-collector-log-forward-es.adoc[leveloffset=+2]
3534
include::modules/cluster-logging-collector-log-forward-fluentd.adoc[leveloffset=+2]

modules/cluster-logging-collector-log-forwarding-about.adoc

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -142,3 +142,9 @@ spec:
142142
** The `outputRefs` is the name of the output to use.
143143
** Optional: A label to add to the logs.
144144

145+
[discrete]
146+
[id="cluster-logging-external-fluentd"]
147+
== Fluentd log handling when the external log aggregator is unavailable
148+
149+
If your external logging aggregator becomes unavailable and cannot receive logs, Fluentd continues to collect logs and stores them in a buffer. When the log aggregator becomes available, log forwarding resumes, including the buffered logs. If the buffer fills completely, Fluentd stops collecting logs. {product-title} rotates the logs and deletes them. You cannot adjust the buffer size or add a persistent volume claim (PVC) to the Fluentd daemon set or pods.
150+

0 commit comments

Comments
 (0)