Skip to content

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

Open
wants to merge 1 commit into
base: logging-docs-6.2-4.17
Choose a base branch
from

Conversation

theashiot
Copy link
Contributor

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 24, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 24, 2025

@theashiot: This pull request references OBSDOCS-1728 which is a valid jira issue.

In response to this:

Version(s): 4.17

Issue: https://issues.redhat.com/browse/OBSDOCS-1728

Link to docs preview:

QE review:

  • QE has approved this change.

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:

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.

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 24, 2025
Copy link
Contributor

@JoaoBraveCoding JoaoBraveCoding left a 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.
Copy link
Contributor

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

Suggested change
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.

Copy link
Contributor Author

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?

Copy link

openshift-ci bot commented Feb 25, 2025

@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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

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

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 9, 2025
@openshift-merge-robot
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants