-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Pavol Loffay <[email protected]>
@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:
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. |
Skipping CI for Draft Pull Request. |
@@ -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. |
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.
@max-cx could you please add a link to the logging docs https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/logging/index ?
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.
@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.
@pavolloffay, you are welcome to close this PR because I have opened #93360 to take this over. |
Version(s):
OCP 4.12-4.19
RHOSDT 3.6
Issue:
https://issues.redhat.com/browse/TRACING-5360
Link to docs preview:
QE review:
Additional information: