Skip to content

BZ202918: Clarify the rebranding still includes Jaeger components. #39611

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

BZ202918: Clarify the rebranding still includes Jaeger components. #39611

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions modules/distr-tracing-rn-new-features.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,13 @@ Result – If changed, describe the current user experience.
[id="distr-tracing-rn-new-features_{context}"]
== New features and enhancements {ProductName} 2.0.0

This release marks the rebranding of Red Hat OpenShift Jaeger to {ProductName}. This effort includes the following:
This release marks the rebranding of Red Hat OpenShift Jaeger to {ProductName}. This name change is to reflect that the distributed tracing solution encompasses more than just Jaeger project components, but also Elasticsearch, AMQ Streams, and OpenTelemetry. The rebranding also allows for new technologies and components to be added in the future under the distributed tracing name.
Copy link

@mwringe mwringe Dec 7, 2021

Choose a reason for hiding this comment

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

I don't know if I would mention Elasticsearch and AMQ stream here. Those are components which we can use with our distributed tracing solution, but they are their own separate components. Elasticsearch and AMQ streams are also not something new with this release or as part of our rebranding.


* Updates {ProductShortName} Operator to Jaeger 1.28. Going forward, {ProductName} will only support the `stable` Operator channel. Channels for individual releases are no longer supported.
This release includes the following:

* Introduces a new OpenTelemetry Operator based on OpenTelemetry 0.33. Note that this Operator is a Technology Preview.
* Updates {ProductShortName} Operator to Jaeger 1.28. Going forward, {ProductName} will only support the `stable` Operator channel. Channels for individual releases are no longer supported.
Copy link

@mwringe mwringe Dec 7, 2021

Choose a reason for hiding this comment

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

We may want to make it more clear that its based on Jaeger 1.28 and not that it is Jaeger 1.28


* Introduces a new OpenTelemetry Operator based on OpenTelemetry 0.33. Note that this Operator is a Technology Preview.
Copy link

@mwringe mwringe Dec 7, 2021

Choose a reason for hiding this comment

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

We shouldn't refer to this as the 'OpenTelemetry Operator', we should refer to this as the 'Red Hat OpenShift distributed tracing data collection' operator which is based on OpenTelemetry 0.33


* Adds support for OpenTelemetry protocol (OTLP) to the Query service.

Expand Down