TRACING-4615: improve OpenTelemetry connectors documentation #82717
Conversation
Signed-off-by: Israel Blancas <iblancas@redhat.com>
openshift-ci-robot
added
the
jira/valid-reference
|
@iblancasa: This pull request references TRACING-4615 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 spike to target the "4.18.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. |
1 similar comment
|
@iblancasa: This pull request references TRACING-4615 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 spike to target the "4.18.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. |
openshift-ci
bot
added
the
size/L
|
🤖 Tue Oct 01 15:35:14 - Prow CI generated the docs preview: |
|
|
||
| - Verify `events.enabled`: ensure that `events.enabled` is set to `true` in the configuration. If this parameter is `false`, event metrics will not be generated. | ||
| + | ||
| - Review event dimensions: make sure that the event attributes you want to track are listed under `events.dimensions`. Only the specified event attributes will be included in the event metrics. |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'in case', 'if', or 'when' rather than 'in the event'. For more information, see RedHat.TermsErrors.
There was a problem hiding this comment.
This term is correct
Signed-off-by: Israel Blancas <iblancas@redhat.com>
|
@iblancasa: The following test failed, say
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. |
4 participants
Version(s): 4.18, 4.17, 4.16, 4.15, 4.14, 4.13, 4.12, 4.11
Issue: TRACING-4615
Link to docs preview:
QE review:
Additional information: this can be added to the latest version of the documentation since it applies to the current RHOSDT version too.