Skip to content
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

LOG-5637: e2e Cluster Logging OTEL support #1684

Merged
merged 1 commit into from
Oct 15, 2024

Conversation

jcantrill
Copy link
Contributor

This PR:

  • describes the Cluster Logging enhancement to support of e2e OTEL semantics

ref: https://issues.redhat.com/browse/LOG-5637

cc @periklis @alanconway @mwringe @xperimental @cahartma @Clee2691 @jgbernalp

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 22, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 22, 2024

@jcantrill: This pull request references LOG-5637 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 epic to target the "4.18.0" version, but no target version was set.

In response to this:

This PR:

  • describes the Cluster Logging enhancement to support of e2e OTEL semantics

ref: https://issues.redhat.com/browse/LOG-5637

cc @periklis @alanconway @mwringe @xperimental @cahartma @Clee2691 @jgbernalp

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.

@jcantrill
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 23, 2024
Copy link
Contributor

@alanconway alanconway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Copy link
Contributor

openshift-ci bot commented Oct 2, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alanconway

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 2, 2024
Copy link
Contributor

@JoaoBraveCoding JoaoBraveCoding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mainly nits and one question

Copy link
Contributor

@periklis periklis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

nit. Replace all references of logging-view-plugin with Logging UIPlugin as the COO resource is called today

@jcantrill
Copy link
Contributor Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 8, 2024

#### Log Visualization

The **Logging UIPlugin** will be modified to replace its UI widgets to rely upon OTEL attributes in lieu of ViaQ. These changes will be

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes will be released to production one release after the other components achieve GA. can you explain this sentence? I think Logging visualization must be ready when the other components achieve GA.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This enhancement provides a path for users to continue to use visualization when there is a mismatch between visualization and what attributes are forwarded by the collector. The intent, as suggested by PM, is to only forward OTEL attributes when GA, allow old data to essentially expire or role off, and then introduce the visualization that only relies upon OTEL attributes.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it, thanks

Copy link
Contributor

@periklis periklis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@JoaoBraveCoding JoaoBraveCoding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just two small comments otherwise lgtm


### API Extensions

During the time this feature is considered Tech Preview, instances of **ClusterLogForwarder** will be [annotated](./forwarder-to-otlp.md) to enable
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like this reference is broken

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am unable to replicate. Viewing the file I am able to navigate to the link.

Comment on lines 127 to 131
kind: ClusterLogForwarder
spec:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add the required tech preview annotation here? Unless I missed it in this document we don't specify what the annotation looks like

Copy link
Contributor

openshift-ci bot commented Oct 15, 2024

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

@alanconway
Copy link
Contributor

/lgtm

@alanconway
Copy link
Contributor

/unhold

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 15, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 7d16351 into openshift:master Oct 15, 2024
2 checks passed
@jcantrill jcantrill deleted the log5637 branch October 15, 2024 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants