[receiver/aerospike] Determine future of component about opentelemetry-collector-contrib HOT 5 OPEN

Pinging code owners:

• receiver/aerospike: @djaglowski @antonblock

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

from opentelemetry-collector-contrib.

@khaf, you previously commented here about the potential root cause of the upgrade problem. Do you still think this is the problem and if so, do you have any hope it will be resolved upstream in the client library?

from opentelemetry-collector-contrib.

Removing unmaintained as a code owner has responded. I understand more discussion is necessary regarding the path forward here, so I'm adding discussion needed. Feel free to correct me if I've missed something.

from opentelemetry-collector-contrib.

@djaglowski I thought adding a package name in the manifest would help, but it didn't. What I'm going to do personally is that I'll try to reproduce the issue in open-telemetry and come up with a fix in the Go client. What I need though is a simple shell incantation that would allow me to reproduce the issue. Appreciate your help.

from opentelemetry-collector-contrib.

@khaf, I noted on the upstream issue here, but I was able to write a unit test which demonstrates the problem. I hope it's helpful. Really appreciate you looking into this.

from opentelemetry-collector-contrib.