Skip to content

OBSDOCS-1722: Port "Troubleshooting log forwarding" to 5.8 and 6.y #89047

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

@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-1722 which is a valid jira issue.

In response to this:

Version(s): 4.17

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

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
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: https://docs.openshift.com/container-platform/4.16/observability/logging/troubleshooting/log-forwarding-troubleshooting.html
Existing file that was copied: https://github.com/openshift/openshift-docs/blob/main/observability/logging/troubleshooting/log-forwarding-troubleshooting.adoc

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
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Feb 24, 2025

🤖 Tue Feb 25 14:20:40 - Prow CI generated the docs preview:
https://89047--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 24, 2025

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

In response to this:

Version(s): 4.17

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

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
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: https://docs.openshift.com/container-platform/4.16/observability/logging/troubleshooting/log-forwarding-troubleshooting.html
Existing file that was copied: https://github.com/openshift/openshift-docs/blob/main/observability/logging/troubleshooting/log-forwarding-troubleshooting.adoc

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 size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 25, 2025
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.

@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.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 28, 2025
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/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants