Skip to content

TRACING-5360: RHOSDT 3.6, Clarify sending logs to lokistack #93342

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 1 commit into
base: main
Choose a base branch
from

Conversation

pavolloffay
Copy link
Member

Version(s):

OCP 4.12-4.19
RHOSDT 3.6

Issue:

https://issues.redhat.com/browse/TRACING-5360

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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

openshift-ci-robot commented May 14, 2025

@pavolloffay: This pull request references TRACING-5360 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.20.0" version, but no target version was set.

In response to this:

Version(s):

OCP 4.12-4.19
RHOSDT 3.6

Issue:

https://issues.redhat.com/browse/TRACING-5360

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 14, 2025
Copy link

openshift-ci bot commented May 14, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label May 14, 2025
@@ -6,7 +6,8 @@
[id="otel-forwarding-logs-to-tempostack_{context}"]
= Forwarding logs to a LokiStack instance

You can deploy the OpenTelemetry Collector to forward logs to a LokiStack instance.
You can deploy the OpenTelemetry Collector to forward logs to a LokiStack instance with `openshift-logging` tenants mode.
For more information about the supported LokiStack configuration refer to the logging documentation.
Copy link
Member Author

Choose a reason for hiding this comment

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

Copy link
Contributor

@max-cx max-cx May 14, 2025

Choose a reason for hiding this comment

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

@pavolloffay, 🙂 unfortunately at this time, the Logging docs pages and URLs are different for different OCP versions and for different Logging versions, unlike our docs that are updated uniformly across all OCP versions. I've tried adding links to my PR, but the docs-building pipelines report errors. It's doable, but it would require an incommensurate amount of effort, which IMHO is not worth it. I'm mentioning that the users need to consult the Logging docs, which is not ideal but as much as is used for a lot of other situations in the OCP docs. I'd leave it at that for now.

@max-cx
Copy link
Contributor

max-cx commented May 14, 2025

@pavolloffay, you are welcome to close this PR because I have opened #93360 to take this over.

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. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants