openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OBSDOCS-1348: Add support exception statement in Logging docs for COO due to its logging UI plugin

Browse Source
This commit is contained in:
Max Leonov
2024-10-09 21:39:37 +02:00
committed by openshift-cherrypick-robot
parent 1952c2a226
commit ea82a1ed32
5 changed files with 29 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
observability/cluster_observability_operator/ui_plugins/logging-ui-plugin.adoc
View File

@@ -6,9 +6,10 @@ include::_attributes/common-attributes.adoc[]
toc::[]
:FeatureName: The {coo-full}
include::snippets/technology-preview.adoc[leveloffset=+2]
[IMPORTANT]
====
Until the approaching General Availability (GA) release of the Cluster Observability Operator (COO), which is currently in link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview] (TP), Red{nbsp}Hat provides support to customers who are using Logging 6.0 or later with the COO for the logging UI plugin on {product-title} 4.14 or later. This support exception is temporary as the COO includes several independent features, some of which are still TP features, but the logging UI plugin is ready for GA.
====
The logging UI plugin surfaces logging data in the {product-title} web console on the *Observe* -> *Logs* page.
You can specify filters, queries, time ranges and refresh rates, with the results displayed as a list of collapsed logs, which can then be expanded to show more detailed information for each log.

9
observability/logging/cluster-logging-support.adoc
View File

@@ -19,7 +19,7 @@ include::snippets/logging-compatibility-snip.adoc[]
* A guaranteed log sink
* Secure storage - audit logs are not stored by default
[id="cluster-logging-support-CRDs"]
[id="cluster-logging-support-CRDs_{context}"]
== Supported API custom resource definitions
LokiStack development is ongoing. Not all APIs are currently supported.
@@ -51,7 +51,12 @@ LokiStack development is ongoing. Not all APIs are currently supported.
include::modules/cluster-logging-maintenance-support-list.adoc[leveloffset=+1]
include::modules/unmanaged-operators.adoc[leveloffset=+1]
[id="cluster-logging-support-must-gather"]
[id="support-exception-for-coo-logging-ui-plugin_{context}"]
== Support exception for the Logging UI Plugin
Until the approaching General Availability (GA) release of the Cluster Observability Operator (COO), which is currently in link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview] (TP), Red{nbsp}Hat provides support to customers who are using Logging 6.0 or later with the COO for its Logging UI Plugin on {product-title} 4.14 or later. This support exception is temporary as the COO includes several independent features, some of which are still TP features, but the Logging UI Plugin is ready for GA.
[id="cluster-logging-support-must-gather_{context}"]
== Collecting logging data for Red Hat Support
When opening a support case, it is helpful to provide debugging information about your cluster to Red{nbsp}Hat Support.

6
observability/logging/logging-6.0/log6x-release-notes.adoc
View File

@@ -39,7 +39,11 @@ In order to continue to use Elasticsearch and Kibana managed by the elasticsearc
* This feature introduces a new architecture for {logging} {for} by shifting component responsibilities to their relevant Operators, such as for storage, visualization, and collection. It introduces the `ClusterLogForwarder.observability.openshift.io` API for log collection and forwarding. Support for the `ClusterLogging.logging.openshift.io` and `ClusterLogForwarder.logging.openshift.io` APIs, along with the Red Hat managed Elastic stack (Elasticsearch and Kibana), is removed. Users are encouraged to migrate to the Red Hat `LokiStack` for log storage. Existing managed Elasticsearch deployments can be used for a limited time. Automated migration for log collection is not provided, so administrators need to create a new ClusterLogForwarder.observability.openshift.io specification to replace their previous custom resources. Refer to the official product documentation for more details. (link:https://issues.redhat.com/browse/LOG-3493[LOG-3493])
* With this release, the responsibility for deploying the {logging} view plugin shifts from the {clo} to the {coo-first}. For new log storage installations that need visualization, the {coo-full} and the associated UIPlugin resource must be deployed. Refer to the xref:../../../observability/cluster_observability_operator/cluster-observability-operator-overview.adoc#cluster-observability-operator-overview[Cluster Observability Operator Overview] product documentation for more details. (link:https://issues.redhat.com/browse/LOG-5461[LOG-5461])
* With this release, the responsibility for deploying the {logging} view plugin shifts from the {clo} to the {coo-first}. For new log storage installations that need visualization, the {coo-full} and the associated `UIPlugin` resource must be deployed. For more information, see xref:log6x-visual.adoc#log6x-visual[Visualization for logging]. (link:https://issues.redhat.com/browse/LOG-5461[LOG-5461])
+
--
include::snippets/logging-support-exception-for-cluster-observability-operator-due-to-logging-ui-plugin.adoc[]
--
* This enhancement sets default requests and limits for Vector collector deployments' memory and CPU usage based on Vector documentation recommendations. (link:https://issues.redhat.com/browse/LOG-4745[LOG-4745])

4
observability/logging/logging-6.0/log6x-visual.adoc
View File

@@ -6,4 +6,6 @@ include::_attributes/common-attributes.adoc[]
toc::[]
Visualization for logging is provided by installing the xref:../../../observability/cluster_observability_operator/cluster-observability-operator-overview.adoc#cluster-observability-operator-overview[Cluster Observability Operator].
Visualization for logging is provided by deploying the xref:../../../observability/cluster_observability_operator/ui_plugins/logging-ui-plugin.adoc#logging-ui-plugin[Logging UI Plugin] of the xref:../../../observability/cluster_observability_operator/cluster-observability-operator-overview.adoc#cluster-observability-operator-overview[Cluster Observability Operator], which requires Operator installation.
include::snippets/logging-support-exception-for-cluster-observability-operator-due-to-logging-ui-plugin.adoc[]

10
snippets/logging-support-exception-for-cluster-observability-operator-due-to-logging-ui-plugin.adoc Normal file
View File

@@ -0,0 +1,10 @@
// Text snippet included in the following assembly:
//
// * observability/logging/logging-6.0/log6x-visual.adoc
:_mod-docs-content-type: SNIPPET
[IMPORTANT]
====
Until the approaching General Availability (GA) release of the Cluster Observability Operator (COO), which is currently in link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview] (TP), Red{nbsp}Hat provides support to customers who are using Logging 6.0 or later with the COO for its xref:../../../observability/cluster_observability_operator/ui_plugins/logging-ui-plugin.adoc#logging-ui-plugin[Logging UI Plugin] on {product-title} 4.14 or later. This support exception is temporary as the COO includes several independent features, some of which are still TP features, but the Logging UI Plugin is ready for GA.
====