This message was deleted.
s
This message was deleted.
b
That's called a distribution. Specifically it is more along the lines of a minus distribution https://opentelemetry.io/docs/concepts/distributions/
Essentially it limits the scope of stuff of the collector to what the vendor needs. You could use the contrib but using the vendors distro typically makes configuration a lot easier
🙌 1
c
I noticed that signoz-otel-collector is behind the contrib progress. Will these two projects eventually align?
s
Yes
c
I’ve now built my own distribution (maybe with some custom proecssor) and referenced signoz-otel-collector and referenced exporter via go mod, but I found that signoz v0.10.1 uses SigNoz/opentelemetry-collector-contrib, it’s quite tedious to synchronize these changes manually
s
We will eventually archive
SigNoz/opentelemetry-collector-contrib
and just continue the development of our distribution. It requires some work before we make the initial release.
c
So for now, recommend using
SigNoz/opentelemetry-collector-contrib
and waiting for the work you mentioned to finish?
We do have plans to customize some processors ourselves, but for now it doesn’t matter, using
SigNoz/opentelemetry-collector-contrib
directly will work just as well