Trying to use my own dummy log receiver with OT collector using custom builder, keep getting this error

[AJ-54]

I am not able to use my own receiver with OT. How can I resolve this error?

How can my receiver use the internal package and how should I import this receiver inside my components.go file of custom OT builder?

[SergeyKanzhelev]

Maybe check here: https://medium.com/opentelemetry/extending-the-opentelemetry-collector-with-your-own-components-64c10cf675db

CC: @jpkrohling

[bogdandrutu]

@djaglowski please help

[djaglowski]

How can my receiver use the internal package

We can discuss extracting an API from the package and making this available outside the contrib collector. There are a small number of structs / methods that would need to be made available. It's ultimately up to the maintainers whether this would be acceptable, but here are a couple details we'd need to iron out:

• Where would be the appropriate place to move this? Possibly a new package called logreceivercreator?
• Probably, this API needs to be marked as experimental, and expectations should be that it will change.

[AJ-54]

@djaglowski For the purpose of developing the receiver locally, I renamed my modules to point at github.com/open-telemetry/opentelemetry-collector-contrib/receiver/dummyreceiver and it is now able to access the internal API's locally. But this also means that the log receiver which is being created using the opentelemetry-log-collection library can only be used inside that GitHub repo.

[djaglowski]

The internal package was not explicitly meant for external consumption. However, as I've noted above, we should be able to extract a public interface from the internal package. This requires buy in from the maintainers, and will take some time to design & implement. I've created #3744 to discuss.

[AJ-54]

Thank you @djaglowski for raising this issue. Really appreciate it.

[jpkrohling]

Internal APIs aren't meant to be consumed by other components. What are you trying to use from that package?

[AJ-54]

HI @jpkrohling, Is there a better way to create my own log receiver?
I see all the log receivers which are out there inside collector-contrib, namely filelogreceiver, tcplogreceiver, syslogreceiver and udplogreceiver uses stanza and other operators from opentelemetry-log-collection library. If these are internal API's, won't that restrict contributions from other individuals?

[jpkrohling]

Sorry, I guess my general answer wasn't a good one for this case. There's apparently something specific to the log components that I'm not aware of.