Track the deprecation of the SkyWalking exporter

[jpkrohling]

Component(s)

exporter/skywalking

Describe the issue you're reporting

I'm listed as the code owner for the SkyWalkling exporter, as I volunteered for it when it was first proposed (#4956). A follow-up PR that was promised at that time (#6116) hasn't been done, and the code owner is not responsive even after being pinged directly.

I would like to start the deprecation process for this component.

• Wait 6 weeks for the code owner to provide feedback, either here or in the linked issue
• Attempt to recruit new code owners, potentially from the SkyWalking community (cc @wu-sheng)
• On Jan 26th, the component will be labeled as unmaintained if the original code owner is still unresponsive and no other code owner for the component has been found
• On June 14th the component will be removed

https://github.com/open-telemetry/opentelemetry-collector#unmaintained

[github-actions]

Pinging code owners:

• exporter/skywalking: @liqiangz

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[wu-sheng]

@liqiangz I think you were keeping eyes on this. How about now?

[wu-sheng]

#6116 @jpkrohling Is there something required in it?

[jpkrohling]

The linked issue is about converting the benchmarks from the original PR into proper Go benchmarks.

[wu-sheng]

I just know these exporters are used by some SkyWalking users, although, SkyWalking has supported Otel native log and metrics formats too.
What do you expect to change? Finish that PR or something else?

[liqiangz]

@jpkrohling @wu-sheng Sorry, someone was assigned this issue before, I didn't pay attention to this issue anymore. I will finish this recently.

[jpkrohling]

What do you expect to change? Finish that PR or something else?

Not only finishing that but handling user's questions related to the components:

https://github.com/open-telemetry/opentelemetry-collector-contrib/issues?q=is%3Aopen+is%3Aissue+label%3Acomp%3Askywalking

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• exporter/skywalking: @liqiangz

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[jpkrohling]

@wu-sheng, @liqiangz , was there any progress on the listed issues?

[wu-sheng]

I think I have answered most of it, and only one is pending as the #26315 is still in review.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• exporter/skywalking: @liqiangz

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[atoulme]

@jpkrohling please follow up on this issue, as #30294 will impact the exporter.

[jpkrohling]

I believe the component is not in a better state than it was since this was first opened. In fact, it's a worse condition, given that the last code owner has been moved to emeritus due to inactivity. It's time to deprecate this component.

[jpkrohling]

Great news to SkyWalking users: you should now rely on SkyWalking's native OTLP ingestion port, as mentioned here: apache/skywalking#11909

Therefore, I think we should remove the SkyWalking exporter without fear that it would badly affect users.

[codeboten]

@jpkrohling the component status was updated to unmaintained on Jan 26, should the timeline in this issue be updated to reflect this?

[jpkrohling]

Done!

[codeboten]

Thanks @jpkrohling

[kellis5137]

You probably don't even want to talk about this, but does it work? did it ever work?

[atoulme]

@jpkrohling it looks like we are past the June 14th date, and it’s time to remove the code.