Skip to content

[enterprise-4.13] OBSDOCS-1413: Document how to verify if receivers/exporters are sending/receiving data based on the OTEL Collector metrics #96317

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

Open
wants to merge 1 commit into
base: enterprise-4.13
Choose a base branch
from

Conversation

max-cx
Copy link
Contributor

@max-cx max-cx commented Jul 18, 2025

…ng/receiving data based on the OTEL Collector metrics

Signed-off-by: Israel Blancas <[email protected]>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 18, 2025

@max-cx: This pull request references OBSDOCS-1413 which is a valid jira issue.

In response to this:

Signed-off-by: Israel Blancas [email protected]

Version(s):

Issue:

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 size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jul 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 18, 2025

@max-cx: This pull request references OBSDOCS-1413 which is a valid jira issue.

In response to this:

Version(s): OCP 4.13

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

Link to docs preview:

QE review: N/A

Additional information: This is a manual cherry-pick of #85688

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 max-cx changed the title OBSDOCS-1413: Document how to verify if receivers/exporters are sending/receiving data based on the OTEL Collector metrics [enterprise-4.13] OBSDOCS-1413: Document how to verify if receivers/exporters are sending/receiving data based on the OTEL Collector metrics Jul 18, 2025
@ocpdocs-previewbot
Copy link

🤖 Fri Jul 18 10:43:49 - Prow CI generated the docs preview:

https://96317--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-troubleshooting.html

Copy link

openshift-ci bot commented Jul 18, 2025

@max-cx: 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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 18, 2025

@max-cx: This pull request references OBSDOCS-1413 which is a valid jira issue.

In response to this:

Version(s): OCP 4.13

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

Link to docs preview:
https://96317--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-troubleshooting.html#exposing-metrics_otel-troubleshoot

QE review: N/A

Additional information: This is a manual cherry-pick of #85688

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
Copy link
Contributor Author

max-cx commented Jul 18, 2025

/label merge-review-needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. merge-review-needed Signifies that the merge review team needs to review this PR size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants