-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OBSDOCS-1728: Port Log visualization to 5.8 #89103
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.
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
base: logging-docs-6.2-4.17
Are you sure you want to change the base?
Conversation
@theashiot: This pull request references OBSDOCS-1728 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a minor comment
|
||
toc::[] | ||
|
||
You can visualize your log data in the {product-title} web console. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just trying to make clearer that this content is "outdated" even if using 5.8. WDYT
You can visualize your log data in the {product-title} web console. | |
You can visualize your log data in the {product-title} web console. See the documentation about "Log visualization with the web console". This page contains instructions on how to configure the **Legacy** log visualizer based on Kibana, meant for use-cases still using ElasticSearch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated with minor changes and also added the deprecation notice about Elasticsearch Operator. WDYT?
a1d526b
to
83694f4
Compare
@theashiot: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
||
toc::[] | ||
|
||
You can visualize your log data in the {product-title} web console.The following section describes configure the legacy log visualizer based on Kibana. The instructions are meant for the use-cases where ElasticSearch is still used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can visualize your log data in the {product-title} web console.The following section describes configure the legacy log visualizer based on Kibana. The instructions are meant for the use-cases where ElasticSearch is still used. | |
You can visualize your log data in the {product-title} web console. The following section describes how to configure the legacy log visualizer based on Kibana. The instructions are meant for the use-cases where ElasticSearch is still used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Elasticsearch support is EOF on Openshift 4.15 for Logging. The elasticsearch are kept for trace. I don't think we need to backport it into Logging 6.2
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Version(s): 4.17
Issue: https://issues.redhat.com/browse/OBSDOCS-1728
Link to docs preview:
QE review:
Additional information: This PR only ports exiting and already published content to a newer release. Content enhancement is beyond the scope of the Jira/PR.
Existing published content:
Existing files that were copied: