-
Notifications
You must be signed in to change notification settings - Fork 250
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
Add a new otelcol.exporter.debug component #301
Add a new otelcol.exporter.debug component #301
Comments
@ptodev could you please assign this to me? I plan to take a stab at it this weekend. |
@BarunKGP - Of course! Thank you! |
@ptodev thanks for assigning this to me! I've already set up the code, and I'll open a PR for it soon. I was wondering whether I should create a separate PR documenting the logging exporter deprecation warning, or would it make sense to simply add it in this one? |
@BarunKGP thank you for your PR! It is ok to add the warning in the same PR (#5867). |
This issue has not had any activity in the past 30 days, so the |
Request
We need to add a new
otelcol.exporter.debug
component based on the debug exporter. We should also deprecateotelcol.exporter.logging
by adding a "warning" message in its doc that the component is deprecated and may be removed around October 2024.Use case
OpenTelemetry Collector's logging exporter has been deprecated in favour of the new debug exporter.
The text was updated successfully, but these errors were encountered: