-
Notifications
You must be signed in to change notification settings - Fork 455
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
update usage of logging exporter #2130
update usage of logging exporter #2130
Conversation
@@ -48,21 +48,21 @@ spec: | |||
timeout: 10s | |||
|
|||
exporters: | |||
logging: | |||
debug: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should reflect this in a changelog? @open-telemetry/operator-approvers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah we should probably changelog this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added changelog
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR changes just docs and e2e tests. Not sure why the changelog is needed. Users defining the logging exporter in their manifests will need to migrate explicitly.
@codeboten is the collector printing a warning if the logging exporter is used? The operator could parse the config and print a warning in the validating webhook.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pavolloffay if the logging exporter is used, it will print out a warning like this:
2023-09-29T08:00:43.970-0700 info exporter/exporter.go:275 Deprecated component. Will be removed in future releases. {"kind": "exporter", "data_type": "traces", "name": "logging"}
2023-09-29T08:00:43.970-0700 info exporter/exporter.go:275 Deprecated component. Will be removed in future releases. {"kind": "exporter", "data_type": "metrics", "name": "logging"}
2023-09-29T08:00:43.972-0700 info exporter/exporter.go:275 Deprecated component. Will be removed in future releases. {"kind": "exporter", "data_type": "logs", "name": "logging"}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This deprecation warning appears for any components that are marked as deprecated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this sounds like a good followup task, but something we can do later
2abbabc
to
eddb9bb
Compare
@codeboten you can update https://github.com/open-telemetry/opentelemetry-operator/blob/main/versions.txt#L5 to 0.86 which will use the latest collector. It should fix failing e2e tests. |
The logging exporter is being deprecated in favour of the debug exporter. This changes references to the logging exporter to use the new debug exporter instead. Note: this will remain in draft until v0.86.0 is released which will be the first release to include the debug exporter. Signed-off-by: Alex Boten <[email protected]>
Signed-off-by: Alex Boten <[email protected]>
Signed-off-by: Alex Boten <[email protected]>
eddb9bb
to
e5b6735
Compare
@pavolloffay rebased and bumped the version. Looks like there's still some failure. Will try to dig into them further |
Signed-off-by: Alex Boten <[email protected]>
Signed-off-by: Alex Boten <[email protected]>
@pavolloffay @jaronoff97 finally got around to fixing the tests. PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this LGTM, I'm going to merge after the tests pass
* update usage of logging exporter The logging exporter is being deprecated in favour of the debug exporter. This changes references to the logging exporter to use the new debug exporter instead. Note: this will remain in draft until v0.86.0 is released which will be the first release to include the debug exporter. Signed-off-by: Alex Boten <[email protected]> * add changelog Signed-off-by: Alex Boten <[email protected]> * update collector version Signed-off-by: Alex Boten <[email protected]> * update expected data Signed-off-by: Alex Boten <[email protected]> * fix test expectations Signed-off-by: Alex Boten <[email protected]> --------- Signed-off-by: Alex Boten <[email protected]>
The logging exporter is being deprecated in favour of the debug exporter. This changes references to the logging exporter to use the new debug exporter instead.
Note: this will remain in draft until v0.86.0 is released which will be the first release to include the debug exporter.