You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some features available in previous releases have been deprecated or removed.
107
+
108
+
Deprecated functionality is still included in OpenShift Logging and continues to be supported; however, it will be removed in a future release of this product and is not recommended for new deployments.
109
+
110
+
[id="openshift-logging-5-2-0-legacy-forwarding"]
111
+
=== Forwarding logs using the legacy Fluentd and legacy syslog methods have been deprecated
112
+
113
+
From {product-title} 4.6 to the present, forwarding logs by using the following legacy methods have been deprecated and will be removed in a future release:
114
+
115
+
* xref:../logging/cluster-logging-external.adoc#cluster-logging-collector-legacy-fluentd_cluster-logging-external[Forwarding logs using the legacy Fluentd method]
116
+
* xref:../logging/cluster-logging-external.adoc#cluster-logging-collector-legacy-syslog_cluster-logging-external[Forwarding logs using the legacy syslog method]
117
+
118
+
Instead, use the following non-legacy methods:
119
+
120
+
* xref:../logging/cluster-logging-external.adoc#cluster-logging-collector-log-forward-fluentd_cluster-logging-external[Forwarding logs using the Fluentd forward protocol]
121
+
* xref:../logging/cluster-logging-external.adoc#cluster-logging-collector-log-forward-syslog_cluster-logging-external[Forwarding logs using the syslog protocol]
{product-title}versions 4.7 and 4.8 support OpenShift Logging versions 5.0, 5.1, and 5.2.
8
+
{product-title} 4.7 and 4.8 support OpenShift Logging 5.0, 5.1, and 5.2.
9
9
10
10
To upgrade from cluster logging in {product-title} version 4.6 and earlier to OpenShift Logging 5.x, you update the {product-title} cluster to version 4.7 or 4.8. Then, you update the following operators:
Copy file name to clipboardExpand all lines: modules/cluster-logging-collector-log-forwarding-supported-plugins-5-1.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
7
7
= Supported log data output types in OpenShift Logging 5.1
8
8
9
-
Red Hat OpenShift Logging version 5.1 provides the following output types and protocols for sending log data to target log collectors.
9
+
Red Hat OpenShift Logging 5.1 provides the following output types and protocols for sending log data to target log collectors.
10
10
11
11
Red Hat tests each of the combinations shown in the following table. However, you should be able to send log data to a wider range target log collectors that ingest these protocols.
12
12
@@ -40,7 +40,7 @@ kafka 2.7.0
40
40
41
41
|====
42
42
43
-
// Note to tech writer, validate these items against the corresponding line of the test configuration file that Red Hat OpenShift Logging version 5.0 uses: https://github.com/openshift/origin-aggregated-logging/blob/release-5.0/fluentd/Gemfile.lock
43
+
// Note to tech writer, validate these items against the corresponding line of the test configuration file that Red Hat OpenShift Logging 5.0 uses: https://github.com/openshift/origin-aggregated-logging/blob/release-5.0/fluentd/Gemfile.lock
44
44
// This file is the authoritative source of information about which items and versions Red Hat tests and supports.
45
45
// According to this link:https://github.com/zendesk/ruby-kafka#compatibility[Zendesk compatibility list for ruby-kafka], the fluent-plugin-kafka plug-in supports Kafka version 0.11.
46
46
// Logstash support is according to https://github.com/openshift/cluster-logging-operator/blob/master/test/functional/outputs/forward_to_logstash_test.go#L37
Copy file name to clipboardExpand all lines: modules/cluster-logging-collector-log-forwarding-supported-plugins-5-2.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
7
7
= Supported log data output types in OpenShift Logging 5.2
8
8
9
-
Red Hat OpenShift Logging version 5.2 provides the following output types and protocols for sending log data to target log collectors.
9
+
Red Hat OpenShift Logging 5.2 provides the following output types and protocols for sending log data to target log collectors.
10
10
11
11
Red Hat tests each of the combinations shown in the following table. However, you should be able to send log data to a wider range target log collectors that ingest these protocols.
12
12
@@ -49,7 +49,7 @@ kafka 2.7.0
49
49
50
50
|====
51
51
52
-
// Note to tech writer, validate these items against the corresponding line of the test configuration file that Red Hat OpenShift Logging version 5.0 uses: https://github.com/openshift/origin-aggregated-logging/blob/release-5.0/fluentd/Gemfile.lock
52
+
// Note to tech writer, validate these items against the corresponding line of the test configuration file that Red Hat OpenShift Logging 5.0 uses: https://github.com/openshift/origin-aggregated-logging/blob/release-5.0/fluentd/Gemfile.lock
53
53
// This file is the authoritative source of information about which items and versions Red Hat tests and supports.
54
54
// According to this link:https://github.com/zendesk/ruby-kafka#compatibility[Zendesk compatibility list for ruby-kafka], the fluent-plugin-kafka plug-in supports Kafka version 0.11.
55
55
// Logstash support is according to https://github.com/openshift/cluster-logging-operator/blob/master/test/functional/outputs/forward_to_logstash_test.go#L37
Copy file name to clipboardExpand all lines: modules/cluster-logging-release-notes-5.1.0.adoc
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,11 @@ Deprecated functionality is still included in OpenShift Logging and continues to
44
44
45
45
With this update, the Elasticsearch Curator has been removed and is no longer supported. Elasticsearch Curator helped you curate or manage your indices on {product-title} 4.4 and earlier. Instead of using Elasticsearch Curator, configure the log retention time.
46
46
47
+
[id="openshift-logging-5-1-0-legacy-forwarding"]
48
+
=== Forwarding logs using the legacy Fluentd and legacy syslog methods have been deprecated
49
+
50
+
From {product-title} version 4.6 to the present, forwarding logs by using the legacy Fluentd and legacy syslog methods have been deprecated and will be removed in a future release. Use the standard non-legacy methods instead.
0 commit comments