Skip to content

OBSDOCS-1681: Port the Configuring LokiStack for OTLP chapter #88649

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

Draft
wants to merge 2 commits into
base: logging-docs-6.2
Choose a base branch
from

Conversation

theashiot
Copy link
Contributor

Version(s): 4.18, 4.17. Note that this needs to be cherry-picked to logging-docs-6.2-4.18, logging-docs-6.2-4.17 release branches and not enterprise-4.18, enterprise-4.17 branches.

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

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: https://docs.openshift.com/container-platform/4.17/observability/logging/logging-6.1/log6x-configuring-lokistack-otlp-6.1.html
Existing file that was copied: https://github.com/openshift/openshift-docs/blob/main/observability/logging/logging-6.1/log6x-configuring-lokistack-otlp-6.1.adoc

@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 14, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 14, 2025

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

In response to this:

Version(s): 4.18, 4.17. Note that this needs to be cherry-picked to logging-docs-6.2-4.18, logging-docs-6.2-4.17 release branches and not enterprise-4.18, enterprise-4.17 branches.

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

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: https://docs.openshift.com/container-platform/4.17/observability/logging/logging-6.1/log6x-configuring-lokistack-otlp-6.1.html
Existing file that was copied: https://github.com/openshift/openshift-docs/blob/main/observability/logging/logging-6.1/log6x-configuring-lokistack-otlp-6.1.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/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 14, 2025
@ocpdocs-previewbot
Copy link

Copy link

openshift-ci bot commented Feb 14, 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.

@theashiot theashiot marked this pull request as draft February 17, 2025 13:33
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 17, 2025
@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 19, 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.

@briandooley briandooley force-pushed the logging-docs-6.2 branch 2 times, most recently from 4742778 to 7976913 Compare February 26, 2025 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. 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