-
Notifications
You must be signed in to change notification settings - Fork 1.9k
OBSDOCS-790: Reorganize OTEL content #71565
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
Conversation
|
@max-cx: This pull request references OBSDOCS-790 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 task to target the "4.16.0" version, but no target version was set. DetailsIn 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. |
|
@max-cx: This pull request references OBSDOCS-790 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 task to target the "4.16.0" version, but no target version was set. DetailsIn 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. |
|
/test all |
|
🤖 Thu Feb 22 16:53:55 - Prow CI generated the docs preview: https://71565--ocpdocs-pr.netlify.app |
97986f5 to
141d92d
Compare
|
@max-cx: This pull request references OBSDOCS-790 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 task to target the "4.16.0" version, but no target version was set. DetailsIn 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. |
|
/test all |
|
/test all |
c03373f to
c55bde9
Compare
|
/test all |
|
/test all |
|
/test all |
|
/test all |
|
@max-cx: This pull request references OBSDOCS-790 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 task to target the "4.16.0" version, but no target version was set. DetailsIn 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. |
|
@max-cx: This pull request references OBSDOCS-790 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 task to target the "4.16.0" version, but no target version was set. DetailsIn 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. |
|
@max-cx: This pull request references OBSDOCS-790 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 task to target the "4.16.0" version, but no target version was set. DetailsIn 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. |
|
Hey @max-cx , Nice work! I went back and forth between the current Tempo and OTEL content, and this PR. That is a lot to keep organized! Well done. I found a couple of small things to consider. I do like the reorganization, and how you've broken out content for sending metrics to the monitoring stack, sending traces and metrics to the Collector, etc. I found that helpful. I'm still in training, so @abrennan89 also needs to review this. |
abrennan89
left a comment
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 initial review done, lmk if you want me to take another look if you implement changes
modules/otel-send-traces-and-metrics-to-otel-collector-without-sidecar.adoc
Show resolved
Hide resolved
abrennan89
left a comment
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.
Added some final / additional comments
979a125 to
95bbc76
Compare
|
/retest |
|
@max-cx: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
|
@max-cx: This pull request references OBSDOCS-790 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 task to target the "4.16.0" version, but no target version was set. DetailsIn 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. |
|
Closing this PR because its commit has been cherry-picked into #72079. |

Version(s):
4.12, 4.13, 4.14, 4.15, 4.16
Issue:
https://issues.redhat.com/browse/OBSDOCS-790
https://issues.redhat.com/browse/OBSDOCS-811
Link to docs preview:
💡 Please note that the
XLsize of this PR is misleading: Because this PR only reorganizes the existing, currently published content across files and TOC menu levels, there is no need to review any of the docs content. What can be reviewed is the following:Changes in the
_topic_maps/_topic_map.ymlfile.The AsciiDoc metadata lines in file headers.
New arrangement of OTEL content in terms of pages and table of contents:

https://71565--ocpdocs-pr.netlify.app/openshift-enterprise/latest/otel/otel-installing
QE review:
Additional information: