OBSDOCS-2675: Modularize otel-config-multicluster.adoc

[kaldesai]

⚠️ Only content movement across files. No new content to review.

Affected Version(s): OCP 4.12+

Tracking JIRAs: https://issues.redhat.com/browse/OBSDOCS-2675

Doc preview: https://102189--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-receiving-telemetry-data.html

SME & QE review: N/A

Additional information:

• Created a new procedure module: modules/otel-receiving-telemetry-data-from-multiple-clusters.adoc.
• Moved the step-by-step procedure content from the otel-receiving-telemetry-data.adoc assembly into the new module.
• Updated the assembly file to include the new procedure module.
• Renamed the assembly file to “Receiving telemetry data” for clarity and consistency
• Added an abstract paragraph to describe the purpose of the assembly.

[openshift-ci-robot]

@kaldesai: This pull request references OBSDOCS-2675 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 sub-task to target the "4.21.0" version, but no target version was set.

In response to this:

⚠️ Only content movement across files. No new content to review.

Affected Version(s): OCP 4.12+

Tracking JIRAs: https://issues.redhat.com/browse/OBSDOCS-2675

Doc preview:

SME & QE review: N/A

Additional information:

• Created a new procedure module: modules/otel-gathering-observability-data-from-multiple-clusters.adoc.
• Moved the step-by-step procedure content from the otel-config-multicluster.adoc assembly into the new module.
• Updated the assembly file to include the new procedure module.
• Renamed the assembly file to “Configuring multicluster observability” for clarity and consistency
• Added an abstract paragraph to describe the purpose of the assembly.

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-robot]

@kaldesai: This pull request references OBSDOCS-2675 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 sub-task to target the "4.21.0" version, but no target version was set.

In response to this:

⚠️ Only content movement across files. No new content to review.

Affected Version(s): OCP 4.12+

Tracking JIRAs: https://issues.redhat.com/browse/OBSDOCS-2675

Doc preview:

SME & QE review: N/A

Additional information:

• Created a new procedure module: modules/otel-gathering-observability-data-from-multiple-clusters.adoc.
• Moved the step-by-step procedure content from the otel-config-multicluster.adoc assembly into the new module.
• Updated the assembly file to include the new procedure module.
• Renamed the assembly file to “Configuring multicluster observability” for clarity and consistency
• Added an abstract paragraph to describe the purpose of the assembly.

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.

[ocpdocs-previewbot]

🤖 Thu Nov 13 15:32:36 - Prow CI generated the docs preview:

https://102189--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-receiving-telemetry-data.html
https://102189--ocpdocs-pr.netlify.app/openshift-enterprise/latest/welcome/learn_more_about_openshift.html

[openshift-ci-robot]

@kaldesai: This pull request references OBSDOCS-2675 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 sub-task to target the "4.21.0" version, but no target version was set.

In response to this:

⚠️ Only content movement across files. No new content to review.

Affected Version(s): OCP 4.12+

Tracking JIRAs: https://issues.redhat.com/browse/OBSDOCS-2675

Doc preview: https://102189--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-config-multicluster.html

SME & QE review: N/A

Additional information:

• Created a new procedure module: modules/otel-gathering-observability-data-from-multiple-clusters.adoc.
• Moved the step-by-step procedure content from the otel-config-multicluster.adoc assembly into the new module.
• Updated the assembly file to include the new procedure module.
• Renamed the assembly file to “Configuring multicluster observability” for clarity and consistency
• Added an abstract paragraph to describe the purpose of the assembly.

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]

Excellent work, Kolyani! Thank you.

As I mentioned in my Jira comment, there is now suddenly new guidance for handling modularization of single-module assemblies, in light of which I am providing some suggestions below:

[openshift-ci-robot]

@kaldesai: This pull request references OBSDOCS-2675 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 sub-task to target the "4.21.0" version, but no target version was set.

In response to this:

⚠️ Only content movement across files. No new content to review.

Affected Version(s): OCP 4.12+

Tracking JIRAs: https://issues.redhat.com/browse/OBSDOCS-2675

Doc preview: https://102189--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-receiving-telemetry-data.html

SME & QE review: N/A

Additional information:

• Created a new procedure module: modules/otel-gathering-observability-data-from-multiple-clusters.adoc.
• Moved the step-by-step procedure content from the otel-config-multicluster.adoc assembly into the new module.
• Updated the assembly file to include the new procedure module.
• Renamed the assembly file to “Configuring multicluster observability” for clarity and consistency
• Added an abstract paragraph to describe the purpose of the assembly.

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-robot]

@kaldesai: This pull request references OBSDOCS-2675 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 sub-task to target the "4.21.0" version, but no target version was set.

In response to this:

⚠️ Only content movement across files. No new content to review.

Affected Version(s): OCP 4.12+

Tracking JIRAs: https://issues.redhat.com/browse/OBSDOCS-2675

Doc preview: https://102189--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-receiving-telemetry-data.html

SME & QE review: N/A

Additional information:

• Created a new procedure module: modules/otel-receiving-telemetry-data-from-multiple-clusters.adoc.
• Moved the step-by-step procedure content from the otel-receiving-telemetry-data.adoc assembly into the new module.
• Updated the assembly file to include the new procedure module.
• Renamed the assembly file to “Receiving telemetry data” for clarity and consistency
• Added an abstract paragraph to describe the purpose of the assembly.

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]

@andreasgerstmayr, WDYT about this wording?

[andreasgerstmayr]

@andreasgerstmayr, WDYT about this wording?

Receiving telemetry data

After setting up the OpenTelemetry collector and instrumenting your application with telemetry, you need to configure the OpenTelemetry collector to receive telemetry data from your cluster.

Receiving telemetry data from multiple clusters

I'd go with "...telemetry data forwarded to a central OpenTelemetry collector instance"

[max-cx]

/retest

[openshift-ci]

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

[max-cx]

/cherry-pick enterprise-4.12

[max-cx]

/cherry-pick enterprise-4.13

[max-cx]

/cherry-pick enterprise-4.14

[max-cx]

/cherry-pick enterprise-4.15

[max-cx]

/cherry-pick enterprise-4.16

[max-cx]

/cherry-pick enterprise-4.17

[max-cx]

/cherry-pick enterprise-4.18

[max-cx]

/cherry-pick enterprise-4.19

[max-cx]

/cherry-pick enterprise-4.20

[openshift-cherrypick-robot]

@max-cx: #102189 failed to apply on top of branch "enterprise-4.12":

Applying: OBSDOCS-2675: Extracted multicluster observability procedure into a new proc module from the assembly
.git/rebase-apply/patch:76: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	_topic_maps/_topic_map.yml
M	welcome/learn_more_about_openshift.adoc
Falling back to patching base and 3-way merge...
Auto-merging welcome/learn_more_about_openshift.adoc
CONFLICT (content): Merge conflict in welcome/learn_more_about_openshift.adoc
Auto-merging _topic_maps/_topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OBSDOCS-2675: Extracted multicluster observability procedure into a new proc module from the assembly

In response to this:

/cherry-pick enterprise-4.12

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.

[max-cx]

/cherry-pick enterprise-4.21

[openshift-cherrypick-robot]

@max-cx: #102189 failed to apply on top of branch "enterprise-4.13":

Applying: OBSDOCS-2675: Extracted multicluster observability procedure into a new proc module from the assembly
.git/rebase-apply/patch:76: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	_topic_maps/_topic_map.yml
M	welcome/learn_more_about_openshift.adoc
Falling back to patching base and 3-way merge...
Auto-merging welcome/learn_more_about_openshift.adoc
CONFLICT (content): Merge conflict in welcome/learn_more_about_openshift.adoc
Auto-merging _topic_maps/_topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OBSDOCS-2675: Extracted multicluster observability procedure into a new proc module from the assembly

In response to this:

/cherry-pick enterprise-4.13

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-cherrypick-robot]

@max-cx: #102189 failed to apply on top of branch "enterprise-4.14":

Applying: OBSDOCS-2675: Extracted multicluster observability procedure into a new proc module from the assembly
.git/rebase-apply/patch:76: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	_topic_maps/_topic_map.yml
M	welcome/learn_more_about_openshift.adoc
Falling back to patching base and 3-way merge...
Auto-merging welcome/learn_more_about_openshift.adoc
CONFLICT (content): Merge conflict in welcome/learn_more_about_openshift.adoc
Auto-merging _topic_maps/_topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OBSDOCS-2675: Extracted multicluster observability procedure into a new proc module from the assembly

In response to this:

/cherry-pick enterprise-4.14

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-cherrypick-robot]

@max-cx: #102189 failed to apply on top of branch "enterprise-4.15":

Applying: OBSDOCS-2675: Extracted multicluster observability procedure into a new proc module from the assembly
.git/rebase-apply/patch:76: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	_topic_maps/_topic_map.yml
M	welcome/learn_more_about_openshift.adoc
Falling back to patching base and 3-way merge...
Auto-merging welcome/learn_more_about_openshift.adoc
CONFLICT (content): Merge conflict in welcome/learn_more_about_openshift.adoc
Auto-merging _topic_maps/_topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OBSDOCS-2675: Extracted multicluster observability procedure into a new proc module from the assembly

In response to this:

/cherry-pick enterprise-4.15

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-cherrypick-robot]

@max-cx: #102189 failed to apply on top of branch "enterprise-4.16":

Applying: OBSDOCS-2675: Extracted multicluster observability procedure into a new proc module from the assembly
.git/rebase-apply/patch:76: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	_topic_maps/_topic_map.yml
M	welcome/learn_more_about_openshift.adoc
Falling back to patching base and 3-way merge...
Auto-merging welcome/learn_more_about_openshift.adoc
CONFLICT (content): Merge conflict in welcome/learn_more_about_openshift.adoc
Auto-merging _topic_maps/_topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OBSDOCS-2675: Extracted multicluster observability procedure into a new proc module from the assembly

In response to this:

/cherry-pick enterprise-4.16

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-cherrypick-robot]

@max-cx: #102189 failed to apply on top of branch "enterprise-4.17":

Applying: OBSDOCS-2675: Extracted multicluster observability procedure into a new proc module from the assembly
.git/rebase-apply/patch:76: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	_topic_maps/_topic_map.yml
M	welcome/learn_more_about_openshift.adoc
Falling back to patching base and 3-way merge...
Auto-merging welcome/learn_more_about_openshift.adoc
CONFLICT (content): Merge conflict in welcome/learn_more_about_openshift.adoc
Auto-merging _topic_maps/_topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OBSDOCS-2675: Extracted multicluster observability procedure into a new proc module from the assembly

In response to this:

/cherry-pick enterprise-4.17

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-cherrypick-robot]

@max-cx: new pull request created: #102482

In response to this:

/cherry-pick enterprise-4.18

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-cherrypick-robot]

@max-cx: new pull request created: #102483

In response to this:

/cherry-pick enterprise-4.19

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-cherrypick-robot]

@max-cx: new pull request created: #102484

In response to this:

/cherry-pick enterprise-4.20

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-cherrypick-robot]

@max-cx: new pull request created: #102485

In response to this:

/cherry-pick enterprise-4.21

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.